gabe-healthlisted

# Gabe Health — Codebase Health Analysis ## Purpose Surface structural fragility in a codebase before it becomes an incident. Find the files that break every sprint, the modules that always change together, and the gaps between what was planned and what was actually touched. This is NOT a code review (use /gabe-review). This is NOT a design critique (use /gabe-roast). This is the X-ray before the surgery — "where is this codebase structurally weak?" --- ## When to Use **Use when:** - Starting a new epic or milestone — know where the minefields are before walking in - During retrospectives — "why did this sprint feel fragile?" - After a production incident — "was this a one-off or is this area inherently unstable?" - Before major refactoring — "which files should I split/stabilize first?" - When things just feel fragile but you can't articulate why **Don't use when:** - Reviewing a specific diff (use /gabe-review) - Looking for bugs in code (use /gabe-roast qa) - Checking alignment with values (use /gabe-align shallow) --- ## Inputs ``` /gabe-health # Full analysis (all 6 checks) /gabe-health hotspots # Churn hotspots only /gabe-health coupling # Coupling clusters only /gabe-health fragile # Bug-fix concentration only /gabe-health gods # God files only /gabe-health scope # Plan vs actual (requires GSD or CE plan) /gabe-health deferred # Deferred items + maintenance staleness /gabe-