Provide consistent, high-signal code reviews by focusing on correctness, clarity, maintainability, security, performance, tests, and developer experience.
Inputs
PR description and linked issues
Code diffs and file context
Existing conventions in the repository
Review Checklist
Correctness
Does the change satisfy the requirements?
Are edge cases handled?
Are errors propagated/handled appropriately?
Readability & Maintainability
Is the code easy to follow?
Are names clear and consistent?
Is complexity justified?
Are public APIs documented?
Security
Validate/encode untrusted input
Avoid leaking secrets/PII
Check authZ/authN boundaries
Performance
Watch for N+1 queries, unnecessary allocations, inefficient loops
Ensure any tradeoffs are explained
Testing
Are tests added/updated?
Do tests cover failure cases and boundaries?
Are tests deterministic and fast?
Style & Consistency
Follows project lint/format rules
No dead code or commented-out blocks
Output Format
Summary of change
Key issues (must-fix)
Suggestions (nice-to-have)
Questions/uncertainties
Tone
Be constructive and specific. Prefer actionable suggestions with examples.
1---2name: code-review-23description: Code Review Skill4---5# Code Review Skill67## Purpose8Provide consistent, high-signal code reviews by focusing on correctness, clarity, maintainability, security, performance, tests, and developer experience.910## Inputs11- PR description and linked issues12- Code diffs and file context13- Existing conventions in the repository1415## Review Checklist16### Correctness17- Does the change satisfy the requirements?18- Are edge cases handled?19- Are errors propagated/handled appropriately?2021### Readability & Maintainability22- Is the code easy to follow?23- Are names clear and consistent?24- Is complexity justified?25- Are public APIs documented?2627### Security28- Validate/encode untrusted input29- Avoid leaking secrets/PII30- Check authZ/authN boundaries3132### Performance33- Watch for N+1 queries, unnecessary allocations, inefficient loops34- Ensure any tradeoffs are explained3536### Testing37- Are tests added/updated?38- Do tests cover failure cases and boundaries?39- Are tests deterministic and fast?4041### Style & Consistency42- Follows project lint/format rules43- No dead code or commented-out blocks4445## Output Format46- Summary of change47- Key issues (must-fix)48- Suggestions (nice-to-have)49- Questions/uncertainties5051## Tone52Be constructive and specific. Prefer actionable suggestions with examples.
Run npx skillmds@latest add jasonkneen/code-review-2 in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.
Code Review Skill It is listed under Coding & Dev Tools on SkillMD.
This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.
This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.
Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.
jasonkneen (@jasonkneen) published this skill. Their other Agent Skills are listed on their SkillMD profile.
jasonkneen