Agent skill · software engineering · samhvw8
code-review
Code review practices with technical rigor and verification gates. Practices: receiving feedback, requesting reviews, verification gates. Capabilities: technical evaluation, evidence-based claims, PR review, subagent-driven review, completion verification. Actions: review, evaluate, verify, validate code changes. Keywords: code review, PR review, pull request, technical feedback, review feedback, completion claim, verification, evidence-based, code quality, review request, technical rigor, subagent review, code-reviewer, review gate, merge criteria. Use when: receiving code review feedback, completing major features, making completion claims, requesting systematic reviews, validating before merge, preventing false completion claims.
Why this skill is useful
Provides structured protocols and evidence-based practices for code review that enhance technical evaluation and verification processes.
What it needs
About 3k tokens when loaded. Last updated 2025-12-09. 10 stars on the source repository.
What this skill does
Code Review Guide proper code review practices emphasizing technical rigor, evidence-based claims, and verification over performative responses. Overview Code review requires three distinct practices: 1. Receiving feedback - Technical evaluation over performative agreement 2. Requesting reviews - Systematic review via code-reviewer subagent 3. Verification gates - Evidence before any completion claims Each practice has specific triggers and protocols detailed in reference files. Core Principle Always honoring YAGNI, KISS, and DRY principles. Be honest, be brutal, straight to the point, and be concise. Technical correctness over social comfort. Verify before implementing. Ask before assuming. Evidence before claims. When to Use This Skill Receiving Feedback Trigger when: Receiving code review comments from any source Feedback seems unclear or technically questionable Multiple review items need prioritization External reviewer lacks full context Suggestion conflicts with existing decisions Reference: references/code-review-reception.md Requesting Review Trigger when: Completing tasks in subagent-driven development (after EACH task) Finishing major features or refactors Before merging to main branch Stuck and need fresh perspective After fixing complex bugs Reference: references/requesting-code-review.md Verification Gates Trigger when: About to claim tests pass, build succeeds, or work is complete Before committing, pushing, or creating PRs Moving to next task Any statement suggesting success/completion Expressing satisfaction with work Reference: references/verification-before-completion.md Quick Decision Tree Receiving Feedback Protocol Response Pattern READ → UNDERSTAND → VERIFY → EVALUATE → RESPOND → IMPLEMENT Key Rules ❌ No performative agreement: "You're absolutely right!", "Great point!", "Thanks for [anything]" ❌ No implementation before verification ✅ Restate requirement, ask questions, push back with technical reasoning, or just start working ✅ If unclear: S …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills samhvw8/code-review