About code-review-excellence
A code review skill for developers and teams reviewing changes or setting review standards. It checks correctness, security, performance, and maintainability, then structures actionable feedback by severity.
Key features
- 01Correctness and security review
- 02Performance and maintainability checks
- 03Severity-based issue grouping
- 04Actionable feedback with rationale
- 05Test and coverage notes
Use cases
- 01Review a pull request or code change
- 02Define team code review standards
- 03Mentor developers with review feedback
- 04Check changes for security or performance risks
Install
Copy the command and run it in a terminal.
$
npx skills add https:/ / github.com/ sickn33/ agentic-awesome-skills --skill code-review-excellenceAfter installing, type/code-review-excellencein Claude Code to confirm it loaded.
Bundled filesresources/implementation-playbook.md
Details
From the project READMECode 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.
Limitations
- Use this skill only when the task clearly matches the scope described above.
- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
Comments
Markdown supported