Code review excellence skill
Transform code reviews from gatekeeping to knowledge sharing through constructive feedback, systematic analysis, and collaborative improvement.
by davila7·MIT license·★ 32,299 Stars on the repo·GitHub ↗
Use now
npx degit davila7/claude-code-templates/cli-tool/components/skills/productivity/code-review-excellence#main ~/.claude/skills/code-review-excellence-davila7Checked ·commit main
Files of Code review excellence
SKILL.md
Show the full text44 lines
Code Review Excellence
Transform code reviews from gatekeeping to knowledge sharing through constructive feedback, systematic analysis, and collaborative improvement.
Use this skill when
- Reviewing pull requests and code changes
- Establishing code review standards
- Mentoring developers through review feedback
- Auditing for correctness, security, or performance
Do not use this skill when
- There are no code changes to review
- The task is a design-only discussion without code
- You need to implement fixes instead of reviewing
Instructions
- Read context, requirements, and test signals first.
- Review for correctness, security, performance, and maintainability.
- Provide actionable feedback with severity and rationale.
- Ask clarifying questions when intent is unclear.
- If detailed checklists are required, open
resources/implementation-playbook.md.
Output Format
- High-level summary of findings
- Issues grouped by severity (blocking, important, minor)
- Suggestions and questions
- Test and coverage notes
Resources
resources/implementation-playbook.mdfor detailed review patterns and templates.
| 1 | |
| 2 | name code-review-excellence |
| 3 | description "Transform code reviews from gatekeeping to knowledge sharing through constructive feedback, systematic analysis, and collaborative improvement." |
| 4 | risk safe |
| 5 | source community |
| 6 | date_added "2026-02-27" |
| 7 | |
| 8 | |
| 9 | # Code Review Excellence |
| 10 | |
| 11 | Transform code reviews from gatekeeping to knowledge sharing through constructive feedback, systematic analysis, and collaborative improvement. |
| 12 | |
| 13 | ## Use this skill when |
| 14 | |
| 15 | Reviewing pull requests and code changes |
| 16 | Establishing code review standards |
| 17 | Mentoring developers through review feedback |
| 18 | Auditing for correctness, security, or performance |
| 19 | |
| 20 | ## Do not use this skill when |
| 21 | |
| 22 | There are no code changes to review |
| 23 | The task is a design-only discussion without code |
| 24 | You need to implement fixes instead of reviewing |
| 25 | |
| 26 | ## Instructions |
| 27 | |
| 28 | Read context, requirements, and test signals first. |
| 29 | Review for correctness, security, performance, and maintainability. |
| 30 | Provide actionable feedback with severity and rationale. |
| 31 | Ask clarifying questions when intent is unclear. |
| 32 | If detailed checklists are required, open `resources/implementation-playbook.md`. |
| 33 | |
| 34 | ## Output Format |
| 35 | |
| 36 | High-level summary of findings |
| 37 | Issues grouped by severity (blocking, important, minor) |
| 38 | Suggestions and questions |
| 39 | Test and coverage notes |
| 40 | |
| 41 | ## Resources |
| 42 | |
| 43 | `resources/implementation-playbook.md` for detailed review patterns and templates. |
| 44 |
Discussion
Alternatives
Browse more free Claude skills or everything in Development.