Reviewing Code

Reviewing Code

The Flow

User: "Review this code..." / "Check this PR..." / "Is this good?"

→ code-foundations classifies as REVIEW
→ cc-quality-practices executes checklists in CHECKER mode
→ Produces severity-tagged findings (VIOLATION/WARNING/PASS)

What the Skill Prevents

Without Skill	With Skill
Vague "looks good"	Checklist-based review
Missing obvious issues	Systematic coverage
Inconsistent review depth	Same rigor every time
"I think this might be a problem"	"This is a VIOLATION because..."

Example Prompt

User: Review this function for quality issues

Claude will:

1. Classify as REVIEW
2. Execute relevant checklists (control flow, data organization, etc.)
3. Produce table output:

Item	Status	Evidence	Location
Nesting depth	WARNING	4 levels	line 45
Parameter count	PASS	3 params	-

See It In Action

• Picker History Review ⭐ - Multi-skill chaining found ID collision risk, 4 violations with fixes
• Picker Text Overflow - Root cause analysis identified pattern inconsistency

Skills Involved

Skill	Role
code-foundations	Classifies task as REVIEW
cc-quality-practices	Executes review checklists
cc-routine-and-class-design	Class/routine design checks
cc-control-flow-quality	Control structure checks
cc-data-organization	Variable/type checks
cc-defensive-programming	Error handling checks