← ClaudeAtlas

debug-sessionlisted

Use when the user reports a bug, error, or unexpected behavior that needs investigation.
joris887/exosuit · ★ 4 · Code & Development · score 74
Install: claude install-skill joris887/exosuit
______________________________________________________________________ ## debug-session **Skill metrics:** Emit a start event to the activity log: ```bash echo "{\"type\":\"skill\",\"event\":\"start\",\"skill\":\"debug-session\",\"ts\":\"$(date -u +%Y-%m-%dT%H:%M:%SZ)\"}" >> docs/sessions/.activity-log.jsonl ``` Debug session for: **$ARGUMENTS** ## Failure State Persistence At each phase transition, write `docs/sessions/.failure-state.md` with YAML frontmatter so the Stop hook and `/continue` can programmatically detect incomplete workflows. **At workflow start** (Phase 1 entry): ```yaml --- status: active skill: debug-session phase: "1" phase_name: "Root Cause Investigation" started_at: "[ISO-8601 timestamp from date -u +%Y-%m-%dT%H:%M:%SZ]" story: "[from $ARGUMENTS — the error description]" branch: "[from git branch --show-current]" next_action: "Reproduce error and trace root cause" files_modified: [] --- ## Context Error: [error description] Root cause: not yet identified Hypothesis: none Fix attempts: 0 Files investigated: [list as investigation proceeds] ``` **At each phase transition:** Update the frontmatter fields: `phase`, `phase_name`, `next_action`, and append to `files_modified`. Update the Context section with investigation progress (root cause, hypothesis, fix attempts). **On successful fix (Phase 5 complete):** Delete `.failure-state.md` — clean state means no failure to recover from. ## Phase 1: Root Cause Investigation (MANDATORY) Do NOT skip thi