Skills
Code review standards skill
What blocker means here: severity definitions and review order the whole team shares.
Last reviewed July 17, 2026
A single-file skill template defining code review standards: the review order, severity definitions with examples, and comment etiquette.
SKILL.md
# Code review standards Apply when reviewing code or responding to review comments. ## Review order Correctness, security, data safety, tests, then style. Never open with style. ## Severity definitions - Blocker: would corrupt data, break users, or open a security hole. Merge stops. - Should-fix: a real defect with a workaround, or missing tests on changed behavior. Fix before merge unless explicitly deferred with a task. - Nit: taste or convention. Never blocks; batch at the end, prefix "nit:". ## Comment etiquette - Quote the exact lines you judge. Findings without line references get ignored. - Every finding proposes a concrete fix or asks a specific question. - Praise real things briefly; skip ceremony. - Disagreements cite the convention or the failure mode, not seniority. ## Verdicts End with: approve, approve with nits, or request changes, plus the single most important item.
Set it up
- 1
Copy the skill body
Align the severity definitions with what your team actually enforces; aspirational strictness erodes fast.
- 2
Create the skill
Add it in the workspace Skills page; the code reviewer agent and any review request follow it.