brutal-honesty-review
Unfiltered critique of code, tests, or claims.
SKILL.md.claude/skills/brutal-honesty-review/SKILL.md
GitHubBrutal Honesty Review
<default_to_action> When brutal honesty is needed: 1. CHOOSE MODE: Linus (technical), Ramsay (standards), Bach (BS detection) 2. VERIFY CONTEXT: Senior engineer? Repeated mistake? Critical bug? Explicit request? 3. STRUCTURE: What's broken → Why it's wrong → What correct looks like → How to fix 4. ATTACK THE WORK, not the worker 5. ALWAYS provide actionable path forwardQuick Mode Selection:
- Linus: Code is technically wrong, inefficient, misunderstands fundamentals
- Ramsay: Quality is subpar compared to clear excellence model
- Bach: Certifications, best practices, or vendor hype need reality check
Calibration:
- Level 1 (Direct): "This approach is fundamentally flawed because..."
- Level 2 (Harsh): "We've discussed this three times. Why is it back?"
- Level 3 (Brutal): "This is negligent. You're exposing user data because..."
DO NOT USE FOR: Junior devs' first PRs, demoralized teams, public forums, low psychological safety
Minimum Findings Enforcement
All brutal honesty reviews enforce a minimum of 3 weighted findings (CRITICAL=3, HIGH=2, MEDIUM=1, LOW=0.5). If the initial review finds fewer, escalate to deeper analysis. Brutally honest reviewers should ALWAYS find something -- if you can't, explain exactly why with evidence. </default_to_action>
The Criticism Structure
## What's Broken
[Surgical description - specific, technical]
## Why It's Wrong
[Technical explanation, not opinion]
## What Correct Looks Like
[Clear model of excellence]
## How to Fix It
[Actionable steps, specific to context]
## Why This Matters
[Impact if not fixed]