← ClaudeAtlas

mkinvestigatelisted

Systematic debugging with root cause investigation. Four phases: investigate, analyze, hypothesize, implement. Iron Law: no fixes without root cause. Use when asked to "debug this", "fix this bug", "why is this broken", "investigate this error", or "root cause analysis". Proactively suggest when the user reports errors, unexpected behavior, or is troubleshooting why something stopped working. NOT for applying fixes without investigation (see mk:fix); NOT for step-by-step evidence-based reasoning (see mk:sequential-thinking).
ngocsangyem/MeowKit · ★ 14 · AI & Automation · score 85
Install: claude install-skill ngocsangyem/MeowKit
<!-- Split for progressive disclosure (checklist #11, #14): 497 → ~65 lines --> <!-- References loaded just-in-time, not all upfront --> # Systematic Debugging > **Path convention:** Commands below assume cwd is `$CLAUDE_PROJECT_DIR` (project root). Prefix paths with `"$CLAUDE_PROJECT_DIR/"` when invoking from subdirectories. **Iron Law: NO FIXES WITHOUT ROOT CAUSE INVESTIGATION FIRST.** ## Skill wiring - **Reads memory:** `.claude/memory/fixes.md`, `.claude/memory/architecture-decisions.md` - **Writes memory:** `.claude/memory/fixes.md` via direct `Edit` (diagnosis records only — `##note:` is a user-typed keyboard shortcut that does NOT fire from agent output; the fix itself is persisted by `mk:fix`). See `.claude/skills/memory/references/capture-architecture.md`. ## Plan-First Gate Investigation precedes planning for bug fixes: 1. Confirm root cause FIRST (Iron Law) 2. After root cause confirmed → invoke `mk:plan-creator --type bugfix` if fix affects > 2 files Skip: Investigation itself doesn't need a plan — it produces the input for planning. ## When to Use - User reports errors, bugs, unexpected behavior - "debug this", "fix this bug", "why is this broken" - "investigate this error", "root cause analysis" - Troubleshooting why something stopped working ## Process 1. **Run preamble** — load `references/preamble.md` and execute the startup bash block 2. **Collect symptoms** — read error messages, stack traces, reproduction steps 3. **Investigate root cause** —