debug-root-cause-analysis
Use when fixing a bug or analyzing a stack trace. Enforces systematic debugging methodology to prevent shotgun debugging and verify fixes.
Use when fixing a bug or analyzing a stack trace. Enforces systematic debugging methodology to prevent shotgun debugging and verify fixes.
Teaches when type assertions are safe versus dangerous in TypeScript. Use when considering using 'as' keyword, type casting, or when working with external data that might use assertions instead of proper validation.
Use when animation "feels wrong" but you can't pinpoint why—debugging floaty movement, stiff characters, unclear action, or any motion that isn't working and needs systematic troubleshooting.
Debug errors from screenshots with deep analysis to fix the immediate issue and proactively identify related errors. Use this when the user provides an error screenshot, says "debug this", or wants to fix runtime/compile errors.
Analyzes iOS test results from xcodebuild test runs. Use immediately after running xcodebuild test, when tests fail, when the user asks to check test results/failures, or when investigating test issues. Automatically locates the latest .xcresult file and presents detailed failure analysis with file locations.
Agente autónomo especializado en auditoría de código (bugs, seguridad, performance).
Detects Ralph Loop completion beyond <promise> tags. Use when checking if a task is complete, verifying completion status, or detecting graceful exit conditions. Implements 4-signal detection: test loops, done signals, completion indicators, and fix plan verification.
4-phase root cause debugging process. Use when fixing bugs or investigating issues.
Debug failed GPU CLI runs. Analyze error messages, diagnose OOM errors, fix sync issues, troubleshoot connectivity, and resolve common problems. Turn cryptic errors into actionable fixes.
eBPF development in Go using github.com/cilium/ebpf (and bpf2go) for tracing and networking (kprobes/uprobes, tracepoints, XDP, TC). Use when writing/reviewing/debugging Go + eBPF code, setting up CO-RE/BTF toolchains, integrating maps and ringbuf/perf events, or diagnosing verifier/load/attach failures on Linux.
Use for bugs, test failures, or unexpected behavior needing root cause
Use at session start for context warm-up and during work to capture decisions
Use when investigating an issue whose origin is unclear, especially when symptoms appear far from the cause. Trigger cues - "bug", "unexpected behavior", "traceback", "why is this happening", "non-deterministic failure". Goal - Trace causality backward to find and validate the true root cause before fixing.
chrome-devtools MCPサーバーを使ったE2Eテストの実施・デバッグを行う。「E2Eテストを実施」「画面をテスト」「ユーザーフローを確認」「ブラウザで動作確認」「画面の表示を検証」などの依頼時に使用。ログインフロー、フォーム送信、ページ遷移などのユーザー操作をインタラクティブにテストする。
CSS performance analysis covering bundle size, selector complexity, render-blocking resources, critical CSS, and optimization strategies. Use when CSS performance is slow or bundle size is too large.
Méthodologie systématique pour identifier la cause d'un bug avant de le corriger. MANDATORY pour bug resolution. À utiliser lors de debugging, bug reports, ou quand l'utilisateur mentionne "bug", "erreur", "ne fonctionne pas", "casse".
This skill should be used when registering hooks, creating custom hooks for module APIs, debugging hook execution, handling async in hooks, or preventing memory leaks from unclean hook removal. Covers Hooks.on/once/call/callAll, lifecycle order, and common pitfalls.
Gates สำหรับตรวจจับ performance regression ผ่าน benchmarks, bundle size, และ load time monitoring
Profile and optimize Python code using cProfile, memory profilers, and performance best practices. Use when debugging slow Python code, optimizing bottlenecks, or improving application performance.
Use when encountering bugs, test failures, unexpected behavior, errors, or performance problems - dispatches systematic-debugging-agent that enforces 4-phase process (root cause investigation, pattern analysis, hypothesis testing, implementation) to prevent quick-fix attempts and ensure proper debugging
Use when optimizing JavaScript/Vue code performance - provides patterns for memory management, component optimization, async handling, bundle size reduction, and common anti-patterns to avoid