bug-fix

Name: bug-fix
Availability: InStock
Author: nextc

Automate end-to-end bug investigation and fix lifecycle across diagnostic phases.

2|Updated Mar 17, 2026

Search Tags:#workflow #debugging #investigation #code-review #bug #hypotheses

Ready to run

npx skills add https://github.com/nextc/nextc-claude --skill bug-fix-nextc

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

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.

Core Features & Use Cases

Phase-driven workflow across Observe, Hypothesize, Investigate, Synthesize & Rebuttal, Fix, Review, Cleanup, Documentation, and Report.
Generates 3 deliberately different hypotheses, gathers FOR and AGAINST evidence in parallel, and uses a rebuttal round to converge on root causes.
Includes automated documentation updates and minimal-change fix discipline to minimize blast radius.

Quick Start

Provide a structured bug report and trigger the Observe phase to begin the diagnostic lifecycle.

Frequently Asked Questions about bug-fix

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I investigate an ambiguous bug when the root cause is unclear?▼

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.

What is the best way to structure an evidence-driven debugging workflow?▼

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.

Can I use a phase-driven process to fix incidents with parallel evidence gathering?▼

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.

How do I minimize blast radius when applying a code fix to a broken system?▼

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.

Does bug diagnosis work without a structured bug report?▼

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.

Why does my debugging process fail to converge on a single root cause?▼

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.