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

Random fixes waste time and create new bugs. Quick patches mask underlying issues.

Debugging sistemático - Análise de root cause em 4 fases

ONLY USE THIS SKILL UPON USER/HOOMAN REQUEST TO USE EXACTLY THIS SKILL, ONLY RUN ON HOOMAN [OK]. Use when encountering a...

Explicit `/systematic-debugging` reference for a structured root-cause audit. Use only when the user requests this workf...

Use for any bug, failing test, build/runtime failure, unexpected behavior, or performance regression; require reproducti...

Root-cause one known bug: reproduce, trace, fix, verify.

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes. Four-phase framework ensuri...

Use when encountering any bug, test failure, or unexpected behavior. 4-phase root cause investigation BEFORE proposing f...

Diagnose a concrete software bug or incident from symptoms, logs, failed tests, or code; verify the cause and, when aske...

Use when encountering a bug, test failure, or unexpected behavior, before proposing fixes

Use when encountering any bug, test failure, or unexpected behavior. ALWAYS find root cause before attempting fixes. Sym...

Use when investigating a bug, test failure, crash, or unexpected behavior, before proposing or applying a fix.

Use when encountering any bug, test failure, or unexpected behavior. 4-phase root cause investigation — NO fixes without...

Systematic root-cause debugging with structured triage. Use when tests fail, builds break, behavior doesn't match expect...

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

Diagnose bugs, failing tests, flaky behavior, build failures, and unexplained performance regressions through reproducti...

Four-phase debugging process - root cause first, then fix. Use when encountering bugs or unexpected behavior.

（中文）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.

When something breaks, the instinct is to start changing code — adding logs, tweaking values, commenting things out. Thi...

遇到任何 bug、测试失败或异常行为时使用，在提出修复方案之前执行

Use on any bug, test failure, or unexpected behavior, before fixes.

Use when encountering any bug, test failure, or unexpected behavior, BEFORE proposing fixes. Four phases — no fixes with...

Use for bugs, test failures, or unexpected behavior needing root cause

Systematic debugging process for any error, test failure, or unexpected behavior. Investigate root cause BEFORE proposin...

Four-phase debugging framework for any technical issue. Use when encountering bugs, errors, or unexpected behavior. Prev...

Beginner-friendly reverse-engineering workflow for Systematic Debugging. Use it to collect evidence, choose static or dy...

Structured debugging workflow adapted for Compiler Driven Development in scala-ts. Use when fixing bugs, investigating w...

Use to find the cause of a failure when it is unclear, after a fix did not hold, or for a flaky or production-only failu...

Use when a failure cause is unclear, an attempted fix failed, or flaky behavior needs investigation. Handle obvious loca...

Apply whenever the task is diagnosing a bug, a failing test, or unexpected behavior — even if the user only says "fix it...

Four-phase debugging framework for any technical issue. Prevents random fix attempts

Four-phase debugging methodology with root cause analysis. Use when investigating bugs, fixing test failures, or trouble...

Use when encountering any bug, test failure, crash, or unexpected behavior in mobile applications — before proposing fix...

Structured 4-phase debugging process — reproduce, isolate, hypothesize, verify — that finds root causes before attemptin...

Use when encountering any bug, test failure, unexpected result, or failed replication - before proposing fixes or explan...

Methodical problem-solving workflow for debugging issues. Use when facing bugs, errors, or unexpected behavior that isn'...

4-phase systematic debugging methodology with root cause analysis and evidence-based verification. Use when debugging co...

Four-phase debugging framework that ensures root cause investigation before attempting fixes. Never jump to solutions. U...

Use when encountering bugs or unexpected behavior. Methodical approach to identify root cause: Reproduce → Isolate → Ide...

Investigates a test failure, bug, or unexpected behavior to find its root cause before proposing any fix - reproduce the...

Find and repair unresolved root causes.

Apply structured debugging techniques to find and fix bugs efficiently. Use when the user reports a bug, encounters unex...

4-phase root cause investigation methodology for bugs and unexpected behavior. Use when tests fail, errors occur, behavi...

当遇到任何 bug、测试失败或非预期行为时，在提出修复方案之前使用

Root-cause debugging in four phases: investigate, analyze, hypothesize, implement. Iron Law -- no fixes without root cau...

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes. Turkish triggers: sistemati...