Code Review Loop

Overview

End-to-end code review etiquette. Covers the requesting side (preparing a PR that's reviewable) and the receiving side (acting on feedback). The skill exists because most code review failures aren't disagreement — they're noise. Reviewers get PRs they can't reasonably review (1500 lines, mixed concerns, no description) and authors get feedback they don't engage with seriously (silent dismissals, "fixed" without explanation, defensive replies). The skill enforces structure on both ends and dispatches claudekit:code-reviewer / claudekit:security-auditor agents on the diff. Used after verification-gate, before merge.

When to Use