Guide engineers through a phase-based debugging workflow to identify root causes.
npx skills add https://github.com/tody-agent/codymaster --skill cm-debugging
Please help me install this Agent Skill. Skill: cm-debugging Source: https://github.com/tody-agent/codymaster/tree/main/skills/cm-debugging Command: npx skills add https://github.com/tody-agent/codymaster --skill cm-debugging
Systematic debugging framework to identify root causes before applying fixes, reducing wasted effort and regression risk.
Describe the issue, reproduce it, then follow Phase 1 through Phase 4 before proposing any fix.
High-intent search queries and answers about installing and using this skill.
A phase-based debugging workflow systematically uncovers root causes before proposing fixes by guiding you through error interpretation, memory integrity checks, evidence gathering, hypothesis testing, and safe implementation across four distinct phases.
To debug a production bug efficiently, describe the issue, reproduce it, and follow a disciplined workflow that mandates root-cause definition and evidence gathering before applying any fix, reducing wasted effort and regression risk.
Yes, this systematic debugging approach applies broadly to test failures, production bugs, performance issues, and integration faults, providing guardrails like mandatory root-cause definition and learning records after fixes.
To reproduce an issue and validate a fix, document findings during evidence gathering, use the cm-tdd skill to create failing tests, then proceed to Phase 4 validation to ensure the root-cause fix is effective.
The best way to prevent regressions is following a disciplined debugging workflow that requires documenting findings, reproducing issues, defining the root cause, creating failing tests, and recording learnings after implementing the fix.
You should gather evidence before proposing a code fix because systematic root-cause identification reduces wasted effort on incorrect solutions and minimizes regression risk by ensuring the actual cause is addressed.
MSBart2Generate failing FanHub tests that reproduce reported bugs.
MomoDavilukeIdentify root causes of bugs and failed tests through a four-phase evidence-driven process.
ShaheerKhawajaOptimize your debugging workflow with actionable insights.
saitarrunDebug intermittent production failures and performance regressions using a structured 6-phase workflow with falsifiable hypotheses and regression tests.
