Code Review
- 196 repo stars
- Updated July 25, 2026
- secondsky/claude-skills
Apply rigorous code-review practices with verification gates, requesting code-reviewer subagent reviews and preventing false completion claims.
About
A skill for code-review practices grounded in technical rigor and verification gates. Developers use it when receiving feedback, requesting code-reviewer subagent reviews, or preventing false completion claims in pull requests.
- Code-review practices
- Verification gates
- code-reviewer subagent
- Prevent false completion claims
Code Review by the numbers
- Data as of Jul 28, 2026 (Skillselion catalog sync)
/plugin marketplace add secondsky/claude-skills/plugin install code-review@claude-skillsAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| repo stars | ★ 196 |
|---|---|
| Last updated | July 25, 2026 |
| Repository | secondsky/claude-skills ↗ |
What it does
Apply rigorous code-review practices with verification gates, requesting code-reviewer subagent reviews and preventing false completion claims.
README.md
Code Review Skill
Technical rigor and evidence-based practices for code review workflows.
Overview
This skill guides proper code review practices emphasizing technical correctness over social comfort, evidence-based claims, and verification before completion. It covers receiving feedback, requesting reviews, and implementing verification gates.
Core Practices
- Receiving Feedback - Technical evaluation over performative agreement
- Requesting Reviews - Systematic review via code-reviewer subagent
- Verification Gates - Evidence before any completion claims
When to Use
- Receiving code review comments (unclear or technically questionable)
- Completing tasks or major features requiring review
- Before making any completion/success claims
- Before committing, pushing, or creating PRs
- Subagent-driven development workflows
Key Principles
- NO performative agreement - No "Great point!" or "You're absolutely right!"
- Verify before implementing - Check suggestions against codebase reality
- Evidence before claims - Run verification commands, read output, THEN claim
- Push back when wrong - Technical correctness over social comfort
Reference Files
references/code-review-reception.md- Receiving feedback protocolreferences/requesting-code-review.md- How to request reviewsreferences/verification-before-completion.md- Verification gates
Auto-Trigger Keywords
- code review
- pull request review
- technical feedback
- verification gates
- completion claims
- subagent review
- merge requirements
- evidence-based development
Source
Adapted from mrgoonie/claudekit-skills
Related skills
Improve Codebase ArchitectureSafely deepen clusters of shallow modules into cohesive, testable units while respecting their external dependencies.531k185k
Caveman ReviewGet ultra-compressed, one-line code review comments that cut noise while keeping every actionable fix.260k92.5kCodebase DesignShared vocabulary for designing deep modules: improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable.233k185kCavecrewDelegate coding tasks to specialized subagents that return compressed output, keeping the main context window usable for much longer sessions.210k92.5k
Requesting Code ReviewDispatch a consistent, high-signal code reviewer subagent that catches plan deviations and quality issues before merging or continuing development.178k260kCode ReviewReviews a branch or PR diff on two axes at once: conformance to coding standards plus a code-smell baseline, and whether it actually implements the original spec.167k185k