What problem does it solve? Developers often jump straight to random fixes when facing bugs or test failures, wasting time on symptoms instead of root causes. This Skill enforces a disciplined investigation loop that requires naming the root cause before any production code changes. ## Core Features & Use Cases - Six-Phase Diagnosis Loop: Reproduce, Minimise, Hypothesise, Instrument, Fix, and Regression Test, with concrete guidance for Java, JUnit, and Spring Boot environments. - Fix Escalation Guard: After three failed fix attempts, the Skill stops further patching and forces a re-examination of architectural assumptions with the human partner. - Learnings Ledger: Reusable pitfalls discovered during diagnosis are appended to .sixth-sense/learnings.jsonl so the same class of bug is never re-diagnosed from scratch. - Use Case: A Spring Boot integration test fails intermittently. The Skill guides you to isolate it with a single JUnit test, form one testable hypothesis from the stack trace, instrument with temporary logging, fix at the narrowest responsible layer, and add a regression test. ## Quick Start Ask the AI to diagnose the failing test or unexpected behavior using the diagnosing-bugs workflow before proposing any fix.