code-review-checklist — Claude Code skill: a checklist for code review
A skill that walks a reviewer through context, functionality, quality, security, performance and tests. Useful on pull requests and audits.
npx claude-code-templates@latest --skill development/code-review-checklistWhat code-review-checklist does
The skill splits a review into six steps. First comes context: what problem the code solves, what the requirements are, which files changed and why. Then functionality, code quality, security, performance and tests, each with its own set of questions so nothing slips through.
Inside are markdown checklists for functionality, security and code quality. Every item comes with a bad-and-good JavaScript pair: missing validation next to email and password-length checks, a concatenated SQL string next to a parameterized query, a hardcoded key next to an environment variable. One example shows a function doing too much, followed by the same logic split into separate calls.
The security checklist names what to look for: input validation, SQL injection and XSS, CSRF, password hashing, token expiry, vulnerable dependencies. That makes the skill worth adding where user input and secrets reach the repository — on a prototype with no external data it adds little.
What it helps with
- walk a pull request through every review step
- catch SQL injection and a hardcoded key before merge
- check that new code has tests and edge cases covered
- set one review standard for a team
- show a newcomer what to look for in someone else's code
Example prompts for the agent
- review this pull request with the code-review-checklist skill
- go through the changes in
src/api/users.jsand flag security issues - review this module: functionality, quality, tests
How to install code-review-checklist
1claude-code-templates
npx claude-code-templates@latest --skill development/code-review-checklist2Skills CLI (Vercel)
npx skills add davila7/claude-code-templates --skill code-review-checklist -a claude-code3Manually: put the files in place
~/.claude/skills/code-review-checklist/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/code-review-checklist/
Manually: put the files in place
.agents/skills/code-review-checklist/SKILL.mdFor all projects use ~/.agents/skills/
Manually: put the files in place
.cursor/skills/code-review-checklist/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install davila7/claude-code-templates code-review-checklist2Manually: put the files in place
.github/skills/code-review-checklist/SKILL.mdPlatform CLI
gemini skills install https://github.com/davila7/claude-code-templates --path cli-tool/components/skills/development/code-review-checklistManually: put the files in place
.devin/skills/code-review-checklist/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about code-review-checklist
How do I install code-review-checklist in Claude?
Use the templates command: npx claude-code-templates@latest --skill development/code-review-checklist. Or run npx skills add davila7/claude-code-templates --skill code-review-checklist -a claude-code. The skill file then sits at ~/.claude/skills/code-review-checklist/SKILL.md.
What does code-review-checklist do?
It gives you a systematic checklist for reviewing code: task context, functionality, quality, security, performance and tests. Each item includes examples of common mistakes and their fixes.
How is it different from just asking the agent to review code?
It sets the order of checks and the questions for each step instead of leaving the review to whatever the agent recalls. That makes the result more consistent across pull requests.