reviewer

Review code diffs against sprint and styleguide checklists with rule-cited findings.

7|2|Updated Apr 28, 2026
One-click install
npx skills add https://github.com/robconery/crap-code --skill reviewer-robconery
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reviewer
Source: https://github.com/robconery/crap-code/tree/main/.pi/skills/reviewer
Command: npx skills add https://github.com/robconery/crap-code --skill reviewer-robconery

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents low-quality or noncompliant code changes by enforcing a strict, sprint-aligned review checklist and producing actionable pass/fail outcomes.

Core Features & Use Cases

  • Sprint checklist enforcement: Evaluates changes against the standing reviewer checklist and sprint-specific requirements.
  • Styleguide and rule-cited findings: Produces findings that cite exact violated rules with file and line references, without rewriting code.
  • Idempotent verdict workflow: Runs a binary gate (pass/fail) and triggers the correct sprint state transition or strike recording with full logging.

Quick Start

Use the reviewer skill to audit a task diff against the Architect’s sprint and styleguide checklists and record a pass or fail with rule-cited findings.

Frequently Asked Questions about reviewer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I enforce a code review checklist against a sprint diff?

To perform deterministic code reviews, the reviewer skill audits task diffs against an Architect-defined rubric, checking structure, naming, boundaries, error handling, logging, and database patterns for strict sprint-aligned compliance.

What is a deterministic code review process for sprint compliance?

A deterministic code review evaluates code diffs against a strict checklist, producing a binary pass/fail verdict with rule-cited findings to prevent noncompliant changes from advancing through sprint gates.

How do I pass styleguide compliance checks for error handling and logging?

To pass styleguide compliance checks, ensure your code diff adheres to the Architect rubric for error handling, logging rules, and naming conventions, avoiding violations that trigger a fail verdict and sprint strike recording.

Does automated code review rewrite code to fix styleguide violations?

Automated code review does not rewrite code; it produces rule-cited findings with exact file and line references for sprint and styleguide violations, leaving code modifications to the developer.

What happens when a code diff fails a sprint gate review?

When a code diff fails a sprint gate review, the process records a strike, appends full rule-cited findings to task logs, and triggers the appropriate sprint state transition to block noncompliant changes.