Awesome-claude-code code-review-standards

Code Review Standards

install
source · Clone the upstream repo
git clone https://github.com/sah1l/awesome-claude-code
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/sah1l/awesome-claude-code "$T" && mkdir -p ~/.claude/skills && cp -r "$T/.claude/skills/code-review-standards" ~/.claude/skills/sah1l-awesome-claude-code-code-review-standards && rm -rf "$T"
manifest: .claude/skills/code-review-standards/SKILL.md
source content

Code Review Standards

Why This Skill Exists

Code reviews are the highest-leverage quality practice — but only when feedback is actionable and categorized by severity. Conventional Comments eliminate the ambiguity of "maybe consider..." style feedback.

Conventional Comments Format

Every review comment MUST use this format:

<label>: <subject>

<optional body — reasoning, links, examples>

Labels (ordered by severity)

LabelMeaningBlocking?
blocker
Must fix before merge — bugs, security issues, data lossYes
issue
Should fix — logic errors, missing edge casesYes
suggestion
Improvement worth considering — better patterns, readabilityNo
nitpick
Style/formatting preference — take it or leave itNo
question
Seeking clarification — not necessarily wrongNo
praise
Highlighting good work — important for moraleNo
thought
Open-ended idea for future considerationNo

Review Modes

Quick Review — scan for blockers and issues only. Use for small PRs, hotfixes, or time-constrained reviews.

Deep Review — full analysis including suggestions, performance, security, and architecture. Use for feature PRs and significant changes.

Rules

  1. Always state the label first — the author should know severity at a glance
  2. Explain WHY, not just WHAT — "this could NPE" → "this could NPE because
    user
    is nullable when fetched from cache (see UserCache.ts:47)"
  3. Offer alternatives — don't just criticize, show a better way
  4. One comment per concern — don't bundle unrelated feedback
  5. Praise good code — reinforces patterns you want to see more of

See examples.md for annotated review comment examples.