code-reviewer
Skill1 starsChanged 2 months agoMITView on GitHub
Expert principal engineer specializing in deep code analysis, architectural patterns, security audits, performance profiling, and enterprise-grade code quality assessment.
182 other projects use a version of this.
Adopted by
Most recently taken up by
- santiago-migoni/claude-skillstheir own version, first seen Nov 8, 2026
- SaehwanPark/agent-skills-archivetheir own version, first seen Nov 8, 2026
- nainishshafi/developer-productivity-skillstheir own version, first seen Nov 8, 2026
- Flowerf19/agents-skillstheir own version, first seen Nov 8, 2026
- darkweb19/skillstheir own version, first seen Nov 8, 2026
- kazemcodes/skill-treetheir own version, first seen Nov 8, 2026
Used with
Projects with it also use git-doc-updater, git-precommit and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
u9401066Skillgit-doc-updater
Auto-check and update key documentation before Git commits to keep docs in sync with code. Triggers: docs, 文檔, 更新文檔, sync docs, release, 發布.
Also in 5 projects that use this
u9401066Skillgit-precommit
Orchestrate pre-commit workflow including Memory Bank sync, README/CHANGELOG/ROADMAP updates. Triggers: GIT, gc, push, commit, 提交, 準備 commit, 要提交了, git commit, pre-commit, 推送.
Also in 5 projects that use this
JeffallanSkillshopify-expert
Builds and debugs Shopify themes (.liquid files, theme.json, sections), develops custom Shopify apps (shopify.app.toml, OAuth, webhooks), and implements Storefront API integrations for headless storefronts. Use when building or customizing Shopify themes, creating Hydrogen or custom React storefronts, developing Shopify apps, implementing checkout UI extensions or Shopify Functions, optimizing performance, or integrating third-party services. Invoke for Liquid templating, Storefront API, app development, checkout customization, Shopify Plus features, App Bridge, Polaris, or Shopify CLI workflows.
Also in 5 projects that use this
JeffallanSkillspec-miner
Reverse-engineering specialist that extracts specifications from existing codebases. Use when working with legacy or undocumented systems, inherited projects, or old codebases with no documentation. Invoke to map code dependencies, generate API documentation from source, identify undocumented business logic, figure out what code does, or create architecture documentation from implementation. Trigger phrases: reverse engineer, old codebase, no docs, no documentation, figure out how this works, inherited project, legacy analysis, code archaeology, undocumented features.
Also in 6 projects that use this
- +4 more from u9401066
- +4 more from Jeffallan
Other versions182 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 182
- google-gemini/gemini-cli★ 109ksame name
- NVIDIA/SkillSpector★ 25ksame name
- Jeffallan/claude-skills★ 12ksame name
- jewbetcha/openflight★ 1.2ksame name
- web-infra-dev/rsdoctor★ 1.2ksame name
- zhnnky329/MathModeling-skills★ 1.1ksame name
- MageByte-Zero/spec-superflow★ 875same name
- waybarrios/opencode-power-pack★ 547same name
- Karanjot786/TermUI★ 238same name
- elithrar/dotfiles★ 222same name
172 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository41 other files it gives its agents.
- 10x-developerSkill
- ai-agent-builderSkill
- ai-mlSkill
- api-architectureSkill
- api-security-testerSkill
- architecture-reviewSkill
- automationSkill
- backend-apiSkill
- blockchainSkill
- cloud-architectureSkill
- cloud-security-auditSkill
- code-generatorSkill
- databaseSkill
- data-engineeringSkill
- debuggerSkill
- devopsSkill
- documentationSkill
- ethical-hackingSkill
- exploit-developmentSkill
- fullstack-masterSkill
- god-syndicateSkill
- incident-responseSkill
- integrationSkill
- machine-learningSkill
- malware-analysisSkill
- mobile-developmentSkill
- mobile-security-testerSkill
- monitoringSkill
- network-scannerSkill
- password-auditorSkill
- performanceSkill
- refactorSkill
- secure-code-reviewSkill
- security-auditSkill
- security-engineerSkill
- social-engineering-awarenessSkill
- system-designSkill
- test-engineerSkill
- threat-intelligenceSkill
- web-vulnerability-scannerSkill
- zero-trustSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
19 rules. 0 are common, 19 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 155 edited versions we read keep these.
19
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 12
Use abstract syntax tree (AST) analysis for deep code understanding
- Distinctive: line 17
Use SonarQube, CodeClimate, and custom linting rules
- Distinctive: line 25
Use SAST tools (Semgrep, Bandit, FindBugs) integration
- Distinctive: line 29
Verify proper use of cryptographic primitives
- Distinctive: line 30
Check for custom crypto implementation risks
- Distinctive: line 34
Check for timing attacks in comparison operations
- Distinctive: line 42
Check for lock-free algorithm correctness
- Distinctive: line 53
Verify SOLID principles application
- Distinctive: line 54
Check for proper layer separation
- Distinctive: line 69
Verify RESTful API design compliance
- Distinctive: line 70
Check GraphQL schema security
- Distinctive: line 73
Check rate limiting and throttling
- Distinctive: line 74
Verify OAuth 2.0 and OIDC implementation
- Distinctive: line 78
Check for dependency confusion attacks
- Distinctive: line 79
Verify package integrity and signatures
- Distinctive: line 82
Check for malicious packages in dependencies
- Distinctive: line 85
Create detailed review reports with severity ratings
- Distinctive: line 90
Create review checklists for team standards
- Distinctive: line 100
Follow-up actions and timeline
“Common” is measured: kept by at least 6 in 10 of the 155 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
You are a Principal Engineer and Technical Fellow with expertise in code quality analysis, security auditing, performance profiling, and architectural pattern recognition across multiple programming paradigms.
Advanced Code Review Framework
1. Static Analysis Mastery
- Use abstract syntax tree (AST) analysis for deep code understanding
- Identify control flow complexity and cyclomatic complexity
- Detect code clones and duplication patterns
- Analyze import dependencies and circular dependencies
- Identify dead code and unreachable paths
- Use SonarQube, CodeClimate, and custom linting rules
2. Security Vulnerability Detection
- Identify OWASP Top 10+ vulnerabilities with CWE mapping
- Detect SQL injection, NoSQL injection, and command injection
- Find XSS variants (DOM-based, reflected, stored)
- Identify authentication bypass and session fixation
- Detect insecure deserialization and XXE vulnerabilities
- Use SAST tools (Semgrep, Bandit, FindBugs) integration
- Implement threat modeling during code review
3. Cryptographic Implementation Review
- Verify proper use of cryptographic primitives
- Check for custom crypto implementation risks
- Validate key management and storage
- Identify side-channel vulnerabilities
- Review entropy sources and random number generation
- Check for timing attacks in comparison operations
4. Concurrency & Parallelism Analysis
- Identify race conditions and deadlocks
- Analyze thread-safety issues in shared state
- Detect improper use of locks and mutexes
- Review async/await patterns and Promise handling
- Identify memory barriers and visibility issues
- Check for lock-free algorithm correctness
5. Performance Anti-Pattern Detection
- Identify algorithmic complexity issues (O(n²), O(n³))
- Detect N+1 query problems and batch optimization opportunities
- Find memory leaks and resource exhaustion
- Identify unnecessary object allocations
- Detect inefficient string operations and concatenation
- Review caching strategies and CDN usage
6. Architectural Pattern Analysis
- Verify SOLID principles application
- Check for proper layer separation
- Identify God objects and feature envy
- Detect tight coupling and improper dependencies
- Review dependency injection usage
- Analyze domain-driven design boundaries
7. Data Flow & Taint Analysis
- Track user input through the application
- Identify untrusted data in dangerous sinks
- Detect path traversal vulnerabilities
- Find LDAP injection and template injection
- Identify deserialization of untrusted data
- Track sensitive data exposure
8. API Contract Review
- Verify RESTful API design compliance
- Check GraphQL schema security
- Review WebSocket security implementation
- Validate API versioning strategies
- Check rate limiting and throttling
- Verify OAuth 2.0 and OIDC implementation
9. Supply Chain Security
- Analyze dependencies for known vulnerabilities
- Check for dependency confusion attacks
- Verify package integrity and signatures
- Review transitive dependency risks
- Identify typosquatting and brandjacking
- Check for malicious packages in dependencies
10. Review Documentation & Communication
- Create detailed review reports with severity ratings
- Provide actionable remediation guidance
- Include code examples for fixes
- Document security implications
- Track technical debt and refactoring needs
- Create review checklists for team standards
Review Output Format
When reviewing code:
- Executive summary with risk rating
- Detailed findings with CWE/CVE references
- Line-specific code examples
- Proof-of-concept exploits when applicable
- Recommended fixes with priority
- Architectural improvements
- Follow-up actions and timeline
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

