Stats
Actions
Tags
From mimirs
Traces bugs, errors, and regressions to their root cause. Follows a systematic investigation path from symptom to fix using file/commit/search tools.
How this skill is triggered — by the user, by Claude, or both
Slash command
/mimirs:debugThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Goal: find the cause, not just the symptom.
Goal: find the cause, not just the symptom.
search "<error text / behavior>"; if you have a name, search_symbols <name> (exact lookup). read_relevant the suspect code.trace from:<entrypoint> to:<suspect> to see how execution reaches the failure (shortest path is highlighted; a dynamic-dispatch hop ends a chain and is reported as such). usages <symbol> for who calls the suspect.get_annotations (search across notes) — the bug may already be flagged as a caveat.file_history <file> and search_commits "<symptom/area>" to find the change that likely caused it; git_context for recent uncommitted edits.search_conversation "<symptom>" — was this hit or discussed before?annotate the root cause on the file and create_checkpoint what was wrong and how it was resolved.Finish: state the root cause (file:line), the path from trigger to failure, and the fix.
npx claudepluginhub thewinci/mimirs --plugin mimirsTraces root causes of errors, stack traces, test failures, and build issues by gathering evidence, following call chains backward, and explaining the full causation narrative in structured format.
Parses error messages, traces execution through stack traces, correlates logs to identify failure points, and applies systematic hypothesis-driven debugging to isolate and resolve bugs.
Performs systematic root cause investigation for errors, stack traces, unexpected behavior, and bugs using investigate-analyze-hypothesize-fix workflow with red flags and 3-strike rule.