83,201 skills sorted by stars.
Root cause analysis for debugging. Use when bugs, test failures, or unexpected behavior have non-obvious causes, or afte...
Use when encountering bugs or unexpected behavior. Methodical approach to identify root cause: Reproduce → Isolate → Ide...
Use when encountering any bug, test failure, or unexpected behavior. ALWAYS find root cause before attempting fixes. Sym...
四阶段调试方法论和根本原因分析。在调查bug、修复测试失败或排查意外行为时使用。强调在根本原因分析之前不要进行修复。
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes - four-phase framework (root...
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes. Four-phase framework ensuri...
Debugging sistemático - Análise de root cause em 4 fases
Systematic methodology for debugging bugs, test failures, and unexpected behavior. Use when encountering any technical i...
Four-phase debugging framework that ensures root cause investigation before attempting fixes. Never jump to solutions.
[Debug] Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes - four-phase framewo...
When something breaks, the instinct is to start changing code — adding logs, tweaking values, commenting things out. Thi...
Four-phase debugging framework that ensures root cause investigation before attempting fixes. Never jump to solutions. U...
4-phase systematic debugging methodology with root cause analysis and evidence-based verification. Use when debugging co...
This skill should be used when encountering any bug, test failure, or unexpected behavior. It requires finding root caus...
(中文)Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
Use for bugs, test failures, or unexpected behavior needing root cause