bugfix-pipeline

Trace active code paths and enforce test-driven reproduction to resolve software defects.

21|2|Updated Mar 12, 2026
One-click install
npx skills add https://github.com/kirillgreen/skills --skill bugfix-pipeline
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bugfix-pipeline
Source: https://github.com/kirillgreen/skills/tree/main/bugfix-pipeline
Command: npx skills add https://github.com/kirillgreen/skills --skill bugfix-pipeline

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill prevents the common failure of fixing code that never actually runs by enforcing a strict, trace-first debugging workflow that ensures changes are applied to the active code path.

Core Features & Use Cases

  • Active Path Tracing: Maps the actual call chain from entry point to root cause, ignoring dead code lookalikes.
  • Test-Driven Reproduction: Requires a failing test to prove the bug exists in the traced path before any code is modified.
  • Safety Gates: Validates that fixes are constrained to the traced files and verifies the full test suite to prevent regressions.

Quick Start

Invoke the bugfix-pipeline skill by typing /bugfix followed by the issue ID or a description of the broken behavior you need to reproduce and resolve.

Frequently Asked Questions about bugfix-pipeline

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

FAQPage Schema
How do I trace active code paths to find a bug in a complex codebase?

Tracing active code paths involves mapping the actual call chain from entry point to root cause, ignoring dead code lookalikes to ensure fixes apply to the code path that actually executes.

What's the best way to reproduce a software defect before modifying code?

Test-driven reproduction requires writing a failing test that proves the bug exists in the traced execution path before modifying any code.

How do I prevent regressions when fixing bugs in complex codebases with similar functions?

Prevent regressions by enforcing safety gates that constrain fixes to traced files and verify the full test suite after resolving the defect.

Does the bugfix pipeline require test-driven development agents to execute the Red-Green-Refactor cycle?

Yes, the bugfix pipeline requires integration with tdd-test-writer and tdd-implementer agents to execute the Red-Green-Refactor cycle within a verified execution path.

Why should I use trace-first debugging instead of directly modifying broken behavior?

Trace-first debugging prevents the failure of fixing code that never actually runs by enforcing a strict workflow ensuring changes apply to the active code path.