Навыки: Разработка

Apply a systematic four-phase debugging workflow when the user asks to debug an issue, investigate a bug, troubleshoot a...

Systematic 4-phase debugging methodology for complex, intermittent, or mysterious issues. Use when investigating bugs, r...

Systematically diagnose unclear product behavior or root cause by building a feedback signal, testing one hypothesis at...

Use when a bug resists the first fix — reproduce it, bisect to the introducing change, test one hypothesis at a time, fi...

Diagnose bugs, test failures, build failures, performance regressions, and unexpected behavior through reproducible evid...

Debug SystemVerilog testbench failures in the SVC project. Use when a testbench fails (make <module>_tb), to analyze CHE...

Full-repo debugging team workflow. Use for 'org run debug', 'org run debug list', or 'org run debug "pasted bug"' reques...

Debug code, analyze errors, interpret stack traces, find root causes, and suggest fixes. Use when troubleshooting bugs,...

Debug and diagnose Thread mesh networks and OpenThread Border Routers. Use when troubleshooting Thread connectivity, ana...

When debugging frustration appears ("why isn't this working?", "it should work", "I don't understand"), orchestrate the...

Triage live outages when the failing component is unknown; localize the fault and route further debugging.

Analyze visual regression test failures in Vizzly. Use when the user mentions failing visual tests, screenshot differenc...

Interactive hypothesis-driven debugging with documented exploration, understanding evolution, and analysis-assisted corr...

Debug pipeline: investigates a bug, diagnoses root cause, writes failing tests, implements fix via TDD, and reviews the...

Evidence-bounded root-cause debugging for observed Z80, ZX Spectrum, or ZX Spectrum Next failures whose cause is unresol...

Debugging specialist for errors, test failures, and unexpected behavior. Use proactively when encountering any issues.

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes - four-phase framework (root...

Debug Godot issues using AgentBridge — use when encountering errors, unexpected behavior, or runtime crashes.

Debugging specialist for errors, test failures, and unexpected behavior in rule processors and Lambda functions

Debugging specialist for root cause analysis and problem resolution

Debugging and troubleshooting specialist with friendly senior developer style (hyung-nim). Use when encountering errors,...

Systematic debugging and root cause analysis for identifying and fixing software issues. Use when: debugging errors, tro...

Systematically debug issues using isolation and evidence-based diagnosis. Follows a structured approach to find root cau...

Investigates bugs using scientific method, manages debug sessions, handles checkpoints. Spawned by /gsd:debug orchestrat...

Use for IDA debugger ops: breakpoints, patches, conditions, patch inventory.

Bug hunter - finds and fixes issues quickly

Use rust-gdb to inspect variables and step through code without modifying it. Prefer it over print debugging for any inv...

Investigate and fix bugs. Use when debugging errors, analyzing stack traces, or tracing code execution. Includes Context...

Diagnoses and fixes runtime errors, type errors, and test failures. Use when there is an error, exception, crash, failin...

⚡ PRIMARY TOOL for: 'why is X broken', 'find bug source', 'root cause analysis', 'trace error', 'debug issue', 'find whe...

Use when the root cause is unclear. Trace the failure back through the call stack and isolate the first bad state.

Hypothesis-driven debugging with systematic investigation. Identifies root causes, creates minimal reproductions, and im...

Systematically analyzes errors, identifies root causes, and suggests targeted fixes with regression safeguards.

Use when a bug, test failure, build break, regression, flaky test, or unexpected behavior appears — before proposing or...

Comprehensive debugging specialist for errors, test failures, log analysis, and system problems. Use when encountering i...

debugging. Use when you need help with debugging.

Use when debugging bugs, test failures, or unexpected behavior. Triggers: 'why isn't this working', 'this doesn't work',...

Debugging conventions for pikru. Use when adding debug traces or investigating issues. Important rule - leave debug trac...

Systematic debugging strategies and error analysis patterns. Auto-triggers when investigating bugs, analyzing stack trac...

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes - four-phase framework (root...

当用户要求"调试这个"、"修复bug"、"排查问题"、"不工作"、"出错了"、"调查问题"、"性能问题"、"类型错误"、"Tauri 通信失败"、"断点调试"、"日志分析"、"性能分析"、"内存泄漏"、"死锁"，或者提到"调试"、"debu...

Debug via reproduce, minimize, observe, hypothesis, instrument, fix, regression-test. Never change random code and hope.

Systematic debugging with four-phase framework + Makerkit-specific patterns. ALWAYS use when encountering bugs, errors,...

Reading errors, troubleshooting, and fixing bugs. Activated when Claude encounters errors or when the user is debugging....

Troubleshoot and fix bugs systematically. Use when errors occur, tests fail, or unexpected behavior is observed. Covers...

Diagnose a defect or unexpected behaviour by reproducing it, reducing the case, tracing the data and proving the fix wit...

Systematic debugging frameworks for finding and fixing bugs - includes root cause analysis, defense-in-depth validation,...

Systematic troubleshooting using the Scientific Method (Observe, Hypothesize, Experiment, Fix).