code-review-excellence
Scannednpx machina-cli add skill bcastelino/agent-skills-kit/code-review-excellence --openclawCode 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.
Source
git clone https://github.com/bcastelino/agent-skills-kit/blob/main/skills/code-review-excellence/SKILL.mdView on GitHub Overview
Code Review Excellence helps teams shift from gatekeeping to knowledge sharing by applying constructive feedback, systematic analysis, and collaborative improvement during pull request reviews. It emphasizes correctness, security, performance, maintainability, and mentoring to uplift code quality without derailing momentum.
How This Skill Works
You start by reading the PR context, requirements, and test signals. You assess code for correctness, security, performance, and maintainability, then deliver actionable feedback with severity levels and reasoning. When intent is unclear, ask clarifying questions and reference the implementation-playbook as needed.
When to Use It
- Reviewing pull requests and code changes
- Establishing code review standards
- Mentoring developers through review feedback
- Auditing for correctness, security, or performance
- Assessing maintainability and long-term impact of changes
Quick Start
- Step 1: Read the PR context, requirements, and test signals.
- Step 2: Review for correctness, security, performance, and maintainability.
- Step 3: Provide actionable feedback with severity and rationale; ask clarifying questions.
Best Practices
- Start by reading context, requirements, and tests to anchor feedback
- Evaluate correctness, security, performance, and maintainability across the change
- Provide actionable feedback with clear severity and rationale
- Ask clarifying questions when intent is unclear to prevent misalignment
- When detailed templates are needed, consult resources/implementation-playbook.md
Example Use Cases
- A reviewer spots a validation gap causing a potential security issue and suggests proper input sanitization and parameterized queries.
- A mentor uses a PR comment to teach a junior developer about meaningful variable naming and edge-case handling.
- A reviewer detects a performance regression and recommends caching or query optimization.
- The team adopts a shared review standard and creates a scoring rubric to harmonize feedback across PRs.
- An audit of a PR’s maintainability leads to refactoring recommendations for clearer interfaces and documentation.
