Code review practices with technical rigor and verification gates. Use for receiving feedback, requesting code-reviewer subagent reviews, or preventing false completion claims in pull requests.
/plugin marketplace add secondsky/claude-skills/plugin install code-review@claude-skillsThis skill inherits all available tools. When active, it can use any tool Claude has access to.
references/code-review-reception.mdreferences/requesting-code-review.mdreferences/verification-before-completion.mdGuide proper code review practices emphasizing technical rigor, evidence-based claims, and verification over performative responses.
Code review requires three distinct practices:
Each practice has specific triggers and protocols detailed in reference files.
Technical correctness over social comfort. Verify before implementing. Ask before assuming. Evidence before claims.
Trigger when:
Reference: references/code-review-reception.md
Trigger when:
Reference: references/requesting-code-review.md
Trigger when:
Reference: references/verification-before-completion.md
SITUATION?
│
├─ Received feedback
│ ├─ Unclear items? → STOP, ask for clarification first
│ ├─ From human partner? → Understand, then implement
│ └─ From external reviewer? → Verify technically before implementing
│
├─ Completed work
│ ├─ Major feature/task? → Request code-reviewer subagent review
│ └─ Before merge? → Request code-reviewer subagent review
│
└─ About to claim status
├─ Have fresh verification? → State claim WITH evidence
└─ No fresh verification? → RUN verification command first
READ → UNDERSTAND → VERIFY → EVALUATE → RESPOND → IMPLEMENT
Full protocol: references/code-review-reception.md
BASE_SHA=$(git rev-parse HEAD~1) and HEAD_SHA=$(git rev-parse HEAD)Full protocol: references/requesting-code-review.md
NO COMPLETION CLAIMS WITHOUT FRESH VERIFICATION EVIDENCE
IDENTIFY command → RUN full command → READ output → VERIFY confirms claim → THEN claim
Skip any step = lying, not verifying
# Tests (prefer bun)
bun test # or: npm test
# Build
bun run build # or: npm run build
# Lint
bun run lint # or: npm run lint
# Type check
bun run typecheck # or: bunx tsc --noEmit
Using "should"/"probably"/"seems to", expressing satisfaction before verification, committing without verification, trusting agent reports, ANY wording implying success without running verification
Full protocol: references/verification-before-completion.md
Verify. Question. Then implement. Evidence. Then claim.
Use when working with Payload CMS projects (payload.config.ts, collections, fields, hooks, access control, Payload API). Use when debugging validation errors, security issues, relationship queries, transactions, or hook behavior.
Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.
Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.