Automate end-to-end bug investigation and fix lifecycle across diagnostic phases.
npx skills add https://github.com/nextc/nextc-claude --skill bug-fix-nextc
Please help me install this Agent Skill. Skill: bug-fix Source: https://github.com/nextc/nextc-claude/tree/main/nextc-core/skills/bug-fix Command: npx skills add https://github.com/nextc/nextc-claude --skill bug-fix-nextc
Evidence-driven bug investigation and fix pipeline. Use when something is broken, not working, or the root cause is ambiguous. Hypothesizes, investigates with parallel agents, fixes, reviews, and updates docs.
Provide a structured bug report and trigger the Observe phase to begin the diagnostic lifecycle.
High-intent search queries and answers about installing and using this skill.
To investigate an ambiguous bug, generate multiple hypotheses and gather parallel evidence for and against each one. Use a rebuttal round to converge on the actual root cause before applying a minimal-change fix to reduce blast radius.
An evidence-driven debugging workflow structures investigation into phases: Observe, Hypothesize, Investigate, Synthesize and Rebuttal, Fix, Review, Cleanup, and Documentation. This ensures formal code review and automated doc updates after fixing.
Yes, a phase-driven process supports incident fixing by running parallel evidence gathering across multiple diagnostic phases. It applies formal reviews and minimal-change discipline to ensure safe, verified resolutions for ambiguous root causes.
To minimize blast radius during a code fix, apply minimal-change discipline by altering only what is necessary to resolve the root cause. Follow up with a formal review phase to verify the fix before cleanup and documentation.
Bug diagnosis requires a structured bug report to trigger the Observe phase effectively. Providing clear initial observations allows the workflow to generate accurate hypotheses and investigate parallel evidence efficiently.
Debugging fails to converge without a rebuttal round to challenge gathered evidence. Generating deliberately different hypotheses and synthesizing for and against evidence ensures formal convergence on the true root cause.
jaydubya818Collect bug details and create a GitHub issue for the compound-engineering plugin.
datorresbOrchestrate codebase assimilation through scan, extract, generate, update, and cleanup phases.
phanijappsReproduce software defects, identify root causes, and implement minimal fixes with regression tests.
BenWork17Guide four-phase debugging with root cause analysis and verification.
