batman-investigatelisted
Install: claude install-skill smhimran/batman
# Batman Investigate
Reconstruct what happened and why; test the explanation against evidence.
## Investigate
1. Establish expected behavior, observed failure, affected users, and timing. Trace the failing request or job through relevant code, logs, and state changes. Recent changes are leads, not proof.
2. Keep plausible causes. For each, identify supporting and conflicting evidence and the smallest check that distinguishes it from alternatives. Seek evidence that could disprove the leading explanation.
3. Reproduce safely when useful. Link the symptom to the failing path and causal mechanism. Distinguish an immediate failure from its underlying cause; a reproduction of the symptom alone does not explain it.
4. Mark what is confirmed, inferred, or unknown. When evidence is unavailable, request the specific trace, input, or timing needed and continue independent work. Do not invent access or rule out an untested cause.
Conclude with the best-supported explanation and its causal evidence. Distinguish locating the failure from explaining its cause. If causes remain unresolved, choose the next discriminating check and identify corroborating evidence needed before confirming the cause; otherwise recommend a repair that addresses the confirmed mechanism. Separate containment from a lasting fix. Stay read-only unless changes are requested; production changes need authorization.
## Keep the work focused
Ground material claims in source, logs, or actual checks; separate facts f