bugfix-workflow

Guide engineers through a six-stage bugfix workflow with TDD and verification.

2|Updated Nov 26, 2025
One-click install
npx skills add https://github.com/penkzhou/swiss-army-knife-plugin --skill bugfix-workflow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bugfix-workflow
Source: https://github.com/penkzhou/swiss-army-knife-plugin/tree/main/swiss-army-knife/skills/bugfix-workflow
Command: npx skills add https://github.com/penkzhou/swiss-army-knife-plugin --skill bugfix-workflow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a standardized 6-stage Bugfix workflow knowledge base, including TDD processes, output format conventions, confidence scoring standards, and general best practices, applicable across backend, frontend, and end-to-end stacks.

Core Features & Use Cases

  • Standardized 6-stage workflow: Red, Green, Refactor with clear checks and validation.
  • TDD guidance: Red-Green-Refactor phases to ensure tests drive changes.
  • Quality gates: Lint and typecheck steps with explicit validation criteria.
  • Universal applicability: Works across all technology stacks (backend/frontend/e2e) and teams.
  • Use Case: When fixing a bug, follow the 6 phases to reproduce, implement, verify, and stabilize the fix with safe rollbacks.

Quick Start

Follow the six-phase bugfix workflow for a reported issue and generate a complete plan and verification steps.

Frequently Asked Questions about bugfix-workflow

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

FAQPage Schema
What is the best way to standardize a bugfix workflow across different software stacks?

A standardized bugfix workflow applies a 6-stage process—reproduce, implement, verify, and stabilize—across backend, frontend, and end-to-end stacks. It enforces deterministic task execution and consistent output formats to improve reliability.

How do I fix a bug using a TDD workflow?

To fix a bug using TDD, follow the Red-Green-Refactor phases: write a failing test to reproduce the issue, implement the minimal code to pass the test, and then refactor. This workflow ensures tests drive the changes safely.

Does a standardized bugfix process work for both frontend and backend applications?

Yes, a standardized bugfix process works universally across all technology stacks, including backend, frontend, and end-to-end scenarios. It guides engineers through reproduction, minimal implementation, and verification regardless of the stack.

How do I enforce lint and typecheck validation during a bugfix?

You enforce lint and typecheck validation by applying quality gates with explicit validation criteria during the bugfix workflow. These steps ensure code quality is maintained alongside the TDD process before stabilizing the fix.

What are the limitations of using a 6-stage bugfix workflow?

The 6-stage bugfix workflow requires strict adherence to its deterministic execution and TDD phases, which may introduce overhead for trivial hotfixes. It is designed for reliable reproduction and verification rather than quick, unverified patches.