ghost-busterslisted
Install: claude install-skill RakamakadoN/ghost-busters-skill
# Ghost Busters — hunting bugs that never crash
## Why this exists
A ghost is a bug that does not fail. It shows 0 instead of an error, "success"
instead of 0 rows, green CI instead of a broken screen, silence instead of an
alarm. In the system this skill was distilled from, not one major incident
raised an exception: a spreadsheet sync lay dead for 4 days, the payment
pipeline stood still for 23 days, three watchdogs wrote into the void for a
year. None were found from a stack trace. All were found by asking "why is it
quiet here?"
**Principle:** ghosts are caught with instruments, not by reading code. Code
shows what *should* happen; production data, logs and history show what *does*.
**Violating the letter of this protocol is violating its spirit.** "Diagnosed
from the code, I'll check production later" is not a diagnosis. It is a hypothesis.
## When to use
- Any "doesn't match": CRM ↔ accounting system, screen ↔ database, plan ↔ fact,
stock ↔ shipments.
- Any "nothing": empty list, 0 money, 0 tasks, no log rows, a cron job that
never speaks.
- Any "after the fix something else got worse".
- Green tests plus a user complaint.
- Proactively: `/ghost-busters raid <area>` — sweep a module against the class
catalogue.
Do not use for a plain feature with no symptom (use your TDD workflow) or for
reviewing a diff (use code review).
**REQUIRED BACKGROUND:** a systematic-debugging discipline (root cause before
fixes). Ghost Busters adds what breaks *silently* on top