Loading...
Loading...
Found 18 Skills
Root-cause discipline for bugs, test failures, and unexpected behavior. Embedded grill on the hypothesis before writing fix code. Use when encountering any bug, failing test, or behavior that doesn't match expectation.
Apply Sherlock Holmes' deductive method to debug code, diagnose system issues, and solve technical puzzles using systematic elimination and logical reasoning
Hard-bug DIAGNOSIS + FIX: reproduce the failure, name the cause, write a regression test, apply the minimal fix. Use whenever the user reports a bug, failure, flaky test, perf regression, error, or visible misbehaviour whose cause is not yet known — even if they only paste a symptom, stack trace, or failing test output, or say "why is X broken", "it stopped working", "it got slower", "this looks wrong". Do NOT start debugging inline without this skill: if your next step would be forming hypotheses about an unexplained failure, invoke /pasteurize first. Do NOT use for review-only diffs (/age), feature design (/mold), fixes where the cause is already known (/cook), or when the user opted out of writes (/culture).
Bug investigation and fix workflow. Triggers: 'debug', 'fix bug', 'investigate issue', 'something is broken', or /debug. Hotfix track for quick fixes, thorough track for root cause analysis. Do NOT use for feature development or refactoring. Do NOT escalate to /ideate unless the fix requires architectural redesign.
Used when performing GDB debugging on target boards via PlatformIO's built-in debugging features, supporting download-and-halt, attach-only, and crash context analysis.
Iterative debugging workflow with confidence scoring and strategic log injection. Five phases: investigate, inject logs, propose fix, verify, cleanup. Use when: debugging unexpected behavior, silent errors, intermittent failures, or issues requiring runtime data. Triggers on "debug", "fix bug", "investigate", "trace issue", "add debug logs", "cleanup debug logs".
Orchestrate multiple specialized agents working in parallel to debug independent problems. Use when encountering 3+ unrelated bugs or test failures in isolated modules. Matches each problem to the right expert agent and launches them concurrently via the Agent tool with worktree isolation. Supports all available subagent types.
Systematically debug issues, investigating bugs, troubleshooting problems, or tracking down errors with persistent state across context resets. Triggers include "debug", "investigate bug", "troubleshoot", "find the problem", "why isn't this working", and "debug session".
Hypothesis-driven autonomous debugging with real command validation
Interactive hypothesis-driven debugging with documented exploration, understanding evolution, and analysis-assisted correction.
Investigate a bug observed in the running application by reading the generated code in plain_modules/, tracing the issue back to the specs, and fixing only the .plain files. Generated code is never modified. Use when the user reports unexpected behavior, visual glitches, crashes, or incorrect logic in the app.
Use this skill to learn using mcp-openmsx tools to control and automate the openMSX emulator, or when interacting with the openMSX emulator for develop/test/debug workflows or interactions that require direct control or information retrieval. Covers all MCP tools. Do NOT use for general agent tasks or when no direct openMSX interaction is required.