nw-bugfix

Automate defect resolution from root-cause analysis to regression testing.

Updated Mar 18, 2024
One-click install
npx skills add https://github.com/v1bh0r/precise-ledger-pro --skill nw-bugfix-v1bh0r
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: nw-bugfix
Source: https://github.com/v1bh0r/precise-ledger-pro/tree/main/nWave/skills/nw-bugfix
Command: npx skills add https://github.com/v1bh0r/precise-ledger-pro --skill nw-bugfix-v1bh0r

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This workflow provides a structured, auditable path for fixing defects, guiding teams from root-cause analysis through user validation to a regression-tested fix implemented via TDD.

Core Features & Use Cases

  • End-to-end defect resolution: RCA, user review, regression tests, and minimal, verifiable fixes.
  • Phase-driven execution: produces RCA documentation, user-approved directions, and a concrete test/fix plan with traceability.
  • Paradigm-aware delivery: integrates with /nw-deliver and adapts to OOP or FP projects, ensuring proper crafter selection and DES-enforced steps.

Quick Start

Describe the defect to start the NW bugfix workflow and guide it through RCA, user review, and regression-deliver.

Frequently Asked Questions about nw-bugfix

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

FAQPage Schema
How do I automate the defect resolution workflow from root-cause analysis to regression testing?

To automate the defect resolution workflow, use a phase-driven execution model that guides teams from root-cause analysis through user validation to regression-tested fixes. This structured path ensures traceable RCA documentation, user-approved directions, and verifiable fixes.

What is the best way to ensure traceability in root-cause analysis for software defects?

Traceability in root-cause analysis is ensured by producing formal RCA documentation, user-approved directions, and a concrete test and fix plan. This phase-driven approach creates an auditable path linking the initial defect to its regression-tested resolution.

Can I apply test-driven development for bugfixes in both OOP and functional programming paradigms?

Yes, you can apply test-driven development for bugfixes in both OOP and functional programming paradigms. The workflow is paradigm-aware, adapting to your project structure to ensure proper crafter selection and enforce appropriate development steps.

How do I implement a structured RCA and user review process before deploying a fix?

Implement a structured RCA and user review process by following a phase-driven execution workflow. This approach generates RCA documentation for review, secures user-approved directions, and creates a concrete test plan before proceeding to minimal, verifiable fixes.

Does the bugfix workflow support integration with delivery systems for orchestrated testing?

Yes, the bugfix workflow supports integration with delivery systems for orchestrated testing. It integrates directly with delivery mechanisms to adapt to OOP or FP projects, ensuring paradigm detection and traceable RCA, tests, and commits.