code-review
/code-review
Conducts and responds to code review — reviewing a change for correctness, design, and risk, and evaluating review feedback received on your own work. Use this before merging, when asked to review a diff or pull request, when review feedback has arrived and needs acting on, or when feedback seems wrong and needs a reasoned response rather than compliance.
- Author
- cbrock84 ↗
- Repository
- headcount ↗
- Licence
- MIT
- Last repository change
- 18.10.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 18.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Conducts and responds to code review — reviewing a change for correctness, design, and risk, and evaluating review feedback received on your own work. Use this before merging, when asked to review a diff or pull request, when review feedback has arrived and needs acting on, or when feedback seems wrong and needs a reasoned response rather than compliance.
Original author description
Conducts and responds to code review — reviewing a change for correctness, design, and risk, and evaluating review feedback received on your own work. Use this before merging, when asked to review a diff or pull request, when review feedback has arrived and needs acting on, or when feedback seems wrong and needs a reasoned response rather than compliance.
How it works
- Reviewing
- Receiving
- Never
SKILL.md preview
--- name: code-review description: Conducts and responds to code review — reviewing a change for correctness, design, and risk, and evaluating review feedback received on your own work. Use this before merging, when asked to review a diff or pull request, when review feedback has arrived and needs acting on, or when feedback seems wrong and needs a reasoned response rather than compliance. --- # Code review Two directions, one skill: reviewing, and being reviewed. ## Reviewing Read the diff against what the change is *for*, not against your preferences. Order matters — spend attention where damage is expensive: 1. **Correctness** — does it do what it claims, including at the boundaries and on the error path? 2. **Blast radius** — what else consumes this? Signature and schema changes are the ones that break things far away. 3. **Security and data** — untrusted input, authorization, anything logged or persisted. 4. **Tests** — do they pin the new behavior, or do they pass regardless? 5. **Design** — will this shape hold under the next change? 6. **Style** — last, and only where a linter cannot. Say which category each comment is, and whether it blocks. A review that mixes a data-loss bug with a naming preference in one undifferentiated list wastes the author's judgment. ## Receiving Feedback is a report of a reader's experience, and that part is always valid — if the reviewer misread it, the code is misleading. The proposed remedy is a separate thing and may be wrong. - **Verify before implementing.** A suggestion that would break behavior gets a reply, not a commit. - **Disagreeing is fine; ignoring is not.** Answer every comment: changed, or why not. - **Do not batch-accept.** Applying every suggestion without judgment is how good code becomes incoherent. - Where a reviewer is factually wrong, show the evidence — the test, the spec, the failing case — rather than asserting. ## Never - Approve your own work, or a change you authored under another name. - Leave a blocking comment without saying what would unblock it. - Rewrite the author's approach in a review comment. Propose it, and let them decide.
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · cbrock84/headcount | 90 | MIT |
| microsoft/aspire | 100 | MIT |
| kdlbs/kandev | 100 | AGPL-3.0 |
| dotnet/runtime | 100 | MIT |
| drosam/agents | 100 | MIT |
| ggml-org/llama.cpp | 100 | MIT |
| ShamelesAbyss/Nyx | 100 | Apache-2.0 |
| dzhng/jevgrep | 100 | MIT |
| iuliandita/skills | 100 | MIT |
Database snapshot: 13.11.2026 · package version ee659b17a4b8 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 2 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 95pr-review
Review a PR for correctness, security, code quality, and testing issues. TRIGGER when user asks to review a PR, check PR quality, or give feedback on a PR. - 90code-review-and-quality
Reviews a diff for correctness, risk, and missing evidence before merge. Use when preparing a change for commit, reviewing a pull request, reviewing AI-generated code, or deciding whether work is genuinely done. - 100local-awesome-code-review-682d95be
Reviews a diff, patch or pull request for correctness, security and team standards, with confidence-scored findings in severity buckets (Critical / Suggestions / Nice to have). Use when asked to review a change, before merging, after finishing a feature, or 'сделай ревью'. Do… - 90code-review-and-quality
Conducts multi-axis code review across correctness, readability, architecture, security, and performance. Use before merging any change. Use when reviewing code written by yourself, another agent, or a human. Triggers on "review my PR", "review this diff", "code review", "review… - 95code-quality-review
[Code Quality] Use when evaluating received review feedback, reviewing named code on request, or verifying a completion claim. Current diffs: changes-review; rationale: why-review. - 95code-quality-review
[Code Quality] Use when evaluating received review feedback, reviewing named code on request, or verifying a completion claim. Current diffs: changes-review; rationale: why-review.