review
the second pair of eyes
review is a loop, not an event: work gets handed over, a reviewer returns findings, and feedback gets absorbed with technical rigor. asking for review, giving review, and receiving review all live behind one trigger. evidence beats agreement: a review without verified findings is noise. live project AGENTS.md and operator directives override this skill.
findings with evidenceseverity firstno rubber stamps
Code review: requesting or delegating a review of uncommitted changes, a diff, or a commit; receiving and acting on review feedback; reviewing GitHub PRs for correctness, security, standards, and AI-slop patterns.
methodology
- read project rules and the requested diff. for a simple change, review directly; delegate an independent boundary when it adds useful evidence.
- another agent delegated the review ->
review-agent: read-only, defect-first, every actionable finding returned. - a GitHub PR is the target ->
review-prfor correctness, security, standards, and scope.--fixchanges code and--replyposts externally; honor current checkout, authority, and explicit communication scope. - feedback lands on you ->
receiving-code-review: verify claims before implementing; never agree performatively or implement blindly. - pending changes, a commit, or a whole-codebase scan ->
ck-code-reviewfor the evidence-based pass. read-only reviews do not create standards docs. - treat the command guides shown here as examples; project rules and trained decisions resolve conflicting steps.
contents
- trainedlearned layer: read first
- requesting-code-reviewdispatching a code-reviewer subagent to verify completed work meets requirements
- review-agentread-only defect-first review of uncommitted changes, a base-branch diff, or a commit
- review-prreviewing a GitHub PR: correctness, security, standards, duplicates, AI-slop; --fix and --reply
- receiving-code-reviewacting on review feedback with technical rigor, no performative agreement
- ck-code-reviewevidence-based review of pending changes, PR numbers, commits, or codebase scans
procedures
procedures the guru runs, one page each. read it, then follow it.
- ck-review-codebase-parallelultrathink edge cases, then parallel verify with code-reviewers
- ck-review-codebasescan and analyze the codebase