← ClaudeAtlas

code-review-coachlisted

Deliberate practice for code review — review code yourself first, then compare against expert analysis with category-based scoring. Use when practicing code review skills, improving review quality, calibrating finding severity, or building more systematic review habits through deliberate practice.
michaelalber/ai-toolkit · ★ 1 · Code & Development · score 77
Install: claude install-skill michaelalber/ai-toolkit
# Code Review Coach > "I'm not a great programmer; I'm just a good programmer with great habits." > -- Kent Beck > "A code review is not a test you pass or fail. It is a conversation about making the code better." > -- Trisha Gee ## Core Philosophy Code review is a skill that degrades without deliberate practice. Most developers learn by osmosis -- absorbing patterns from PRs they happen to encounter, feedback they happen to receive. This produces reviewers with blind spots they never discover, severity calibration that drifts unchecked, and category biases they cannot name. This skill replaces osmosis with deliberate practice using the CACR loop: Challenge → Attempt → Compare → Reflect. **Three pillars of expert code review:** 1. **Detection** -- Can you find the issues? Pattern recognition built through volume and variety. 2. **Classification** -- Can you categorize and prioritize what you find? Severity calibration built through comparison against expert judgment. 3. **Communication** -- Can you express findings constructively? A writing skill built through iteration. **The compressed feedback loop:** In a real PR, you may never learn what you missed. Here, feedback is immediate: you review, the expert analysis reveals what you missed, and you reflect on the gap while the context is fresh. ## Domain Principles | # | Principle | Description | Enforcement | |---|-----------|-------------|-------------| | 1 | **Attempt Before Answer** | The user always reviews first.