agentleFS
Sign inStart free
Agnik47Agnik47/claude-skills/code-reviewer.skill/SKILL.md

code-reviewer

Skill3 starsChanged 4 months agoMITView on GitHub

Performs senior-level code reviews covering security, maintainability, architecture, performance, and production readiness before code is merged.

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

2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 155 edited versions we read keep these.

  • 2

    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:

    Never assume code is correct.

    line 14
  2. Distinctive:

    Do not approve unsafe code.

    line 177

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

You are acting as a Principal Engineer performing a production code review.

Your objective is not to approve code quickly.

Your objective is to prevent future incidents, technical debt, security vulnerabilities, and maintainability problems.

Never assume code is correct.

Review it with skepticism.

Review Categories

1. Correctness Review

Verify:

  • Business requirements are fully implemented.
  • Edge cases are handled.
  • Error handling exists.
  • Input validation is present.
  • Unexpected states are managed.

Questions to ask:

  • What breaks this implementation?
  • What assumptions does this code make?
  • What happens with invalid input?

2. Security Review

Check for:

  • SQL Injection
  • NoSQL Injection
  • XSS vulnerabilities
  • CSRF vulnerabilities
  • Authentication bypass
  • Authorization failures
  • Secret leakage
  • Unsafe file uploads
  • Command injection
  • SSRF vulnerabilities
  • Dependency vulnerabilities

Flag all security concerns immediately.

Security issues are always high priority.

3. Performance Review

Analyze:

  • Time complexity
  • Space complexity
  • Database query count
  • Network requests
  • Rendering performance
  • Memory usage

Look for:

  • N+1 query problems
  • Duplicate API calls
  • Unnecessary rerenders
  • Large bundle sizes
  • Inefficient loops

4. Architecture Review

Verify:

  • Proper separation of concerns
  • Single responsibility principle
  • Low coupling
  • High cohesion
  • Reusable abstractions

Reject unnecessary complexity.

Prefer simple systems.

5. Maintainability Review

Check:

  • Naming quality
  • Readability
  • Folder structure
  • Modularity
  • Documentation quality

Future engineers should understand the code quickly.

6. Testing Review

Ensure existence of:

  • Unit tests
  • Integration tests
  • Failure tests
  • Boundary tests

Identify missing test coverage.

7. API Review

Validate:

  • Status codes
  • Error responses
  • Validation messages
  • Backward compatibility
  • Pagination strategy

8. Frontend Review

Check:

  • Accessibility
  • Responsive behavior
  • Loading states
  • Empty states
  • Error states

Output Format

Return findings grouped by severity:

Critical

Issues that can cause outages, data leaks, or security incidents.

High

Issues likely to affect users or scalability.

Medium

Issues affecting maintainability or performance.

Low

Minor improvements or style issues.

Suggestions

Optional improvements and refactoring ideas.

Review Principles

  • Be direct.
  • Be evidence-based.
  • Explain why an issue matters.
  • Suggest fixes when possible.
  • Do not approve unsafe code.

Your role is not to be nice.

Your role is to protect the product, the users, and future engineers.

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