Loading...
Loading...
Found 24 Skills
Debug experiment code with structured error analysis. Categorize errors, apply targeted fixes with retry logic, and use reflection to prevent recurring issues. Use when experiment code fails or produces incorrect results.
Guide for debugging issue on a specific code sections, pattern, or files. Used this skill when user asking for assistant when debugging an issues or explaining a code.
Use when encountering BUILD FAILED, test crashes, simulator hangs, stale builds, zombie xcodebuild processes, "Unable to boot simulator", "No such module" after SPM changes, or mysterious test failures despite no code changes - systematic environment-first diagnostics for iOS/macOS projects
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.
Identify and debug performance regressions from code changes. Use comparison and profiling to locate what degraded performance and restore baseline metrics.
Gemini CLI consultation workflow for coding agents. Use when technical tasks need Gemini consultation for decisions, planning, debugging, problem-solving, or pre-implementation guidance.
Research MQL5 documentation (Japanese and English only) for MQL5 creation/editing issues, compile errors, or API questions. Use when users ask to look up docs, interpret MQL5 errors, or confirm correct language usage. Sources limited to https://www.mql5.com/ja/docs and https://www.mql5.com/en/docs.
Use when ANY iOS build fails, test crashes, Xcode misbehaves, or environment issue occurs before debugging code. Covers build failures, compilation errors, dependency conflicts, simulator problems, environment-first diagnostics.
RubyMine Ruby IDE with Rails support. Use for Ruby development.
Full 5-layer analysis of a specific function. Use when debugging or deeply understanding code.
Debug applications using the dbg CLI debugger. Supports Node.js (V8/CDP), Bun (WebKit/JSC), and native code via LLDB (DAP). Use when: (1) investigating runtime bugs by stepping through code, (2) inspecting variable values at specific execution points, (3) setting breakpoints and conditional breakpoints, (4) evaluating expressions in a paused context, (5) hot-patching code without restarting (JS/TS), (6) debugging test failures by attaching to a running process, (7) debugging C/C++/Rust/Swift with LLDB, (8) any task where understanding runtime behavior requires a debugger. Triggers: "debug this", "set a breakpoint", "step through", "inspect variables", "why is this value wrong", "trace execution", "attach debugger", "runtime error", "segfault", "core dump".
Chain-of-Verification (CoVe) prompting system. Converts lazy prompts into rigorous 4-stage verified output. Use for any code generation, debugging, or implementation task. Automatically invoked by wavybaby for medium/high complexity tasks. Reduces hallucinations and catches subtle bugs.