agentleFS
Sign inStart free
Cor-IncorporatedCor-Incorporated/claude-code-skills/skills/code-reviewer/SKILL.md

code-reviewer

Skill5 starsChanged 2 months agoMITView on GitHub

Review code for quality, security, and best practices across TypeScript, JavaScript, Python, Go, Swift, and Kotlin. Analyzes PRs with automated scripts (pr_analyzer, code_quality_checker, review_report_generator), checks for OWASP vulnerabilities, validates naming/structure/error handling, and generates actionable review reports. Use when: reviewing a pull request, providing code feedback, checking code quality before merge, auditing security of changes. Do NOT use for: writing new code, fixing bugs (use /bugfix), generating tests, or architectural design (use /modern-architecture).

182 other projects use a version of this.

Adopted by

Most recently taken up by

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.
  • u9401066Skill

    git-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

  • u9401066Skill

    git-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

  • JeffallanSkill

    shopify-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

  • JeffallanSkill

    spec-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

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 155 edited versions we read keep these.

  • 1

    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
  1. Distinctive:

    No hardcoded secrets, API keys, or tokens </important>

    line 44

“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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Code Reviewer

Review code for quality, security, and correctness. Generate actionable reports with severity-ranked findings.

<important if="reviewing a pull request or checking code quality before merge"> ## Review Workflow

1. Analyze Changes

Identify the scope: PR diff, staged changes, or specified files.

# PR analysis
python ${CLAUDE_SKILL_DIR}/scripts/pr_analyzer.py <project-path> [options]

# Code quality scan
python ${CLAUDE_SKILL_DIR}/scripts/code_quality_checker.py <target-path> [--verbose]
</important><important if="reviewing code for correctness, security, or quality issues"> ### 2. Check Against Standards

Review each changed file for:

Correctness

  • Logic errors, off-by-one, null/undefined handling
  • Race conditions in async code
  • Edge cases not covered</important>
<important if="auditing security of code changes or checking for OWASP vulnerabilities"> **Security (OWASP)** - Input validation (Zod schemas for all user input) - SQL injection (parameterized queries only) - XSS prevention (no `dangerouslySetInnerHTML` without sanitization) - Authentication/authorization checks on every route - No hardcoded secrets, API keys, or tokens </important><important if="checking code quality, structure, or naming conventions"> **Quality** - Functions under 50 lines, files under 800 lines - Nesting under 4 levels - Immutable patterns (`return { ...obj, field }`, no mutations) - Consistent naming with existing codebase - No `console.log` in production code

Testing

  • New code has corresponding tests
  • Tests are falsifiable (see /test-falsify)
  • Edge cases covered</important>
<important if="generating a code review report or producing review output"> ### 3. Generate Report
python ${CLAUDE_SKILL_DIR}/scripts/review_report_generator.py [arguments] [options]

Report Format

## Code Review: [PR/Change Title]

### Summary
[1-2 sentence overview of changes and overall assessment]

### Findings

#### CRITICAL (block merge)
| # | File | Line | Issue | Fix |
|---|------|------|-------|-----|

#### HIGH (fix before merge)
| # | File | Line | Issue | Fix |
|---|------|------|-------|-----|

#### MEDIUM (fix recommended)
| # | File | Line | Issue | Fix |
|---|------|------|-------|-----|

#### LOW (suggestion)
| # | File | Line | Issue | Fix |
|---|------|------|-------|-----|

### Verdict
- [ ] CRITICAL: 0
- [ ] HIGH: 0
- [ ] Approve / Request Changes
</important><important if="encountering issues running review scripts or handling large PRs"> ## Error Handling
SituationAction
Script fails to runFall back to manual review using Grep/Read
PR too large (100+ files)Split review by directory; prioritize security-sensitive files
Cannot determine intent of changeAsk the author for context before reviewing
Conflicting patterns in codebaseFlag inconsistency; recommend which pattern to follow
</important><important if="classifying review findings by severity or deciding merge readiness"> ## Severity Definitions
LevelCriteriaAction
CRITICALSecurity vulnerability, data loss risk, production breakageBlock merge
HIGHBug, missing validation, missing error handlingFix before merge
MEDIUMCode smell, missing test, inconsistent patternFix recommended
LOWStyle, naming, minor improvementOptional
</important>

References

  • references/code_review_checklist.md -- Detailed checklist by category
  • references/coding_standards.md -- Language-specific standards
  • references/common_antipatterns.md -- Anti-patterns with examples
  • Global coding style: ~/.claude/rules/coding-style.md

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.

Check your setup, free