Skill library / Claude Code

Code Review skill for Claude Code

A code review skill gives Claude Code a consistent checklist so every review covers the same ground, from injection risks to missing tests, and ranks findings so you fix the critical ones first.

What it's good for

• Self-review before opening a PR
• Reviewing a teammate's branch locally
• Enforcing team conventions that linters can't catch

How the skill works

1. Run git diff (or read the PR diff) to scope the change
2. Read surrounding code for context before judging a line
3. Check correctness, security, error handling, performance and tests
4. Group findings as Blocker / Should fix / Nit with file:line references
5. Suggest a concrete fix or code snippet for each Blocker

Built-in rules

• Don't comment on formatting a formatter would fix
• Never approve changes that lack tests for new logic without saying so
• Quote the exact line you're commenting on

Example

You: “/code-review”
Result: A prioritised list: 1 blocker (unescaped SQL in users.ts:42) with a fix, 3 should-fix items and 2 nits.

SKILL.md template

Save as code-review/SKILL.md.

---
name: code-review
description: "Reviews staged changes or a pull request for bugs, security issues, performance and readability, and outputs prioritised, actionable comments. Use when the user asks to review code, a diff, a PR, or says 'check my changes'."
---

# Code Review

## Workflow
1. Run git diff (or read the PR diff) to scope the change
2. Read surrounding code for context before judging a line
3. Check correctness, security, error handling, performance and tests
4. Group findings as Blocker / Should fix / Nit with file:line references
5. Suggest a concrete fix or code snippet for each Blocker

## Rules
- Don't comment on formatting a formatter would fix
- Never approve changes that lack tests for new logic without saying so
- Quote the exact line you're commenting on

How to install in Claude Code

Unzip into .claude/skills/ in your project (or ~/.claude/skills/ for all projects) and invoke it with /skill-name.

Pro tip

Put your style guide in references/conventions.md; the skill only loads it when reviewing, so it doesn't bloat every session.

FAQ

Related skills

• Commit Message skill for Claude Code
• API Documentation skill for Claude Code
• Pull Request Description skill for Claude Code