Require a written root-cause and falsification test before code changes.
npx skills add https://github.com/hbvg234/jnmt.vn --skill debug-protocol-hbvg234
Please help me install this Agent Skill. Skill: debug-protocol Source: https://github.com/hbvg234/jnmt.vn/tree/main/Claude-code/.claude/skills/debug-protocol Command: npx skills add https://github.com/hbvg234/jnmt.vn --skill debug-protocol-hbvg234
Solves the problem of rushing fixes by requiring a written root-cause and falsification test before any code changes.
Activate the lightweight auto-trigger when an error occurs and follow the four phases to investigate root cause before proposing any fix.
High-intent search queries and answers about installing and using this skill.
Falsification testing validates debugging hypotheses by attempting to disprove them before fixing code. You form a hypothesis about an error, test conditions that should falsify it, and only proceed with a fix if the hypothesis survives, ensuring accurate root-cause identification.
The four phases of structured software debugging are reproducing and locating the error, forming a hypothesis, testing the hypothesis through falsification, and finally fixing and verifying the solution. This workflow reduces regression risk and improves overall debugging quality.
To stop developers from rushing code fixes during failing tests, implement an auto-triggered guidance system requiring written root-cause documentation before code changes. This enforces a four-phase investigation process to ensure disciplined problem-solving and reduce regression risk.
Yes, structured debugging works for unexpected software behavior without explicit errors. The investigation workflow is applicable during any abnormal behavior, requiring you to reproduce the issue, form hypotheses, and validate fixes before committing changes, ensuring thorough quality assurance.
The best way to reduce regression risk when fixing bugs is to follow a four-phase investigation process requiring written root-cause analysis and falsification tests before modifying code. This structured approach ensures fixes are validated against the actual problem.
derHakenTrace data flow and apply a four-phase process to fix root causes.
aist-ai-sastDiagnose MCP regression failures and implement durable fixes across test suites.
leynosFormulate falsifiable debugging hypotheses and plan falsification tests for software issues.
paopp2Enforces a four-phase workflow for root-cause analysis of software issues before fixes are allowed.
