bug-fix

Diagnose software defects via root-cause triage and regression testing.

18|1|Updated Jan 3, 2026
One-click install
npx skills add https://github.com/nexus-substrate/nexus-agents --skill bug-fix-nexus-substrate
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bug-fix
Source: https://github.com/nexus-substrate/nexus-agents/tree/main/skills/bug-fix
Command: npx skills add https://github.com/nexus-substrate/nexus-agents --skill bug-fix-nexus-substrate

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The bug-fix Skill helps you reliably resolve defects without compounding failures by enforcing a disciplined workflow: stop early on failures, diagnose the root cause, add a regression test, and verify everything end-to-end.

Core Features & Use Cases

  • Stop-the-Line Protocol: Prevents symptom-level edits by freezing changes when tests/builds/lint fail and capturing the exact evidence needed to debug correctly.
  • Triage Sequence: Guides reproduction, localization to the causal layer, minimal failing cases, and root-cause fixes instead of speculative refactors.
  • Regression Guard & Verification: Requires a regression test and reruns the full check suite to ensure the fix is durable.
  • Use Case: When a CI failure appears after a merge (e.g., a race condition causing a hang or timeout), apply the triage steps to isolate the real causal layer, implement the minimal root-cause fix, and add a test that would have caught it earlier.

Quick Start

Use the bug-fix skill when you see a “fix bug” style request or a failing test/build, and ask your agent to reproduce the issue, diagnose the causal layer, implement the minimal root-cause fix, add a regression test, and verify with the full lint/typecheck/test suite.

Frequently Asked Questions about bug-fix

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

FAQPage Schema
How do I fix CI failures caused by race conditions after a merge?

Fix CI failures by enforcing a stop-the-line protocol that freezes changes on test or build failures, triages the root cause across affected layers, implements a minimal fix, and adds a regression test. This prevents compounding failures from speculative edits.

What's the best way to debug failing tests without introducing new issues?

Debug failing tests by capturing exact evidence, localizing the failure to its causal layer, reducing to a minimal failing case, and verifying the root-cause fix end-to-end with lint, typecheck, and test suites. This disciplined workflow ensures durable bug resolution.

Can I use a test-driven workflow to fix lint and typecheck issues?

Yes, you can fix lint and typecheck issues using a test-driven workflow that requires reproducing the issue, localizing the failure, adding a regression guard, and running full verification suites. This applies across UI, service, data, and external dependency layers.

How do I isolate the root cause of a hanging or timing out build?

Isolate root causes of hanging builds by applying a triage sequence: reproduce the failure, localize it to the causal layer, reduce it to a minimal failing case, and implement a minimal root-cause fix. End-to-end verification ensures the hang is resolved.

When should I not use speculative refactors to resolve software defects?

Avoid speculative refactors when resolving software defects because they bypass root-cause triage. Instead, freeze changes upon failure, collect reproducible evidence, and apply minimal edits directly to the causal layer to ensure the fix is durable.