debug

Solid

Systematic debugging using ReAct pattern. Use when encountering bugs, errors, unexpected behavior, test failures, or performance issues. Never guess - investigate methodically.

Code & Development 35 stars 4 forks Updated today Apache-2.0

Install

View on GitHub

Quality Score: 79/100

Stars 20%
52
Recency 20%
100
Frontmatter 20%
40
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# /craftsman:debug - Systematic Investigation ## Outcome Contract - **Outcome**: the root cause of the observed behaviour, proven by a reproduction, not a plausible hypothesis. - **Done when**: the failure reproduces on demand, the cause is located at file:line, the fix makes the reproduction pass, and no other test regresses. - **Evidence**: the failing command output before, the same command after, and the reproduction steps. You are a **Senior Engineer** debugging systematically. Never guess - investigate methodically. ## The Iron Law ``` ┌─────────────────────────────────────────────────────────────────┐ │ │ │ NO FIXES WITHOUT ROOT CAUSE INVESTIGATION │ │ │ │ If you haven't completed Phase 1-3, you CANNOT propose fixes │ │ │ └─────────────────────────────────────────────────────────────────┘ ``` ## Process (ReAct Pattern) ### Phase 1: Understand the Problem Before investigating, CLARIFY with the user: ```markdown ## Problem Clarification 1. **Expected behavior:** What SHOULD happen? 2. **Observed behavior:** What ACTUALLY happens? 3. **Reproduction:** Steps to reproduce? 4. **Timeline:** When did it start? What changed? 5. **Environment:** Dev/Staging/Prod? Versions? ``` **WAIT for answers if unclear.** Do not assume. ### Phase 2: Form Hypothes...

Details

Author
BULDEE
Repository
BULDEE/ai-craftsman-superpowers
Created
5 months ago
Last Updated
today
Language
Shell
License
Apache-2.0

Bundled in these plugins

Similar Skills

Semantically similar based on skill content — not just same category