Debug
Trace a bug, error, or regression to its root cause. Use when investigating a failure, a stack trace, unexpected behavior, or "why does X happen".From its SKILL.md
npx -y skills add TheWinci/mimirs --skill debugAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
SKILL.md
1.2 KB, as published. Nobody here has run it
Debug
Goal: find the cause, not just the symptom.
- Locate the symptom —
search "<error text / behavior>"; if you have a name,search_symbols <name>(exact lookup).read_relevantthe suspect code. - Follow the path —
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. - Known issues —
get_annotations(search across notes) — the bug may already be flagged as a caveat. - When introduced —
file_history <file>andsearch_commits "<symptom/area>"to find the change that likely caused it;git_contextfor recent uncommitted edits. - Past attempts —
search_conversation "<symptom>"— was this hit or discussed before? - Fix & record — once fixed,
annotatethe root cause on the file andcreate_checkpointwhat was wrong and how it was resolved.
Finish: state the root cause (file:line), the path from trigger to failure, and the fix.