blind-spot-breakerlisted

# Blind Spot Breaker When you review code you just wrote (or just read), your judgment shares the same mental model that produced it — you notice what you expected to see, not what's actually there. This skill breaks that by forcing four hostile personas, each with a different fear and a different definition of "broken," and requiring every one of them to find something. There is no "LGTM" exit. **Credit:** the three-persona structure (Saboteur, New Hire, Security Auditor) and the severity-promotion mechanic are adapted from the `adversarial-reviewer` skill in Alireza Rezvani's [claude-skills](https://github.com/alirezarezvani/claude-skills) `engineering-skills` plugin (MIT licensed). This version is an independent rewrite in this repo's house style, with a fourth persona (The On-Call Engineer, for production operability) added. ## When To Use - Before merging any PR, especially one with no human reviewer - When a review is about to be a rubber stamp ("looks fine to me") - After a long session — fatigue produces blind spots this compensates for - On security- or reliability-sensitive code: auth, payments, data access, anything a pager could go off for - Whenever something "feels off" and that instinct deserves fifteen more minutes ## Review Workflow ### 1. Gather the changes - No target given → `git diff` (unstaged) + `git diff --cached` (staged). If both are empty, `git diff HEAD~1`. - A ref/range given → `git diff <ref>`. - A specific file given → read the **entire f