skills.rest
wonder-zhang
wonder-zhangCOMMUNITY
Explore all skills by this author →
GitHub

bugfix

Automate end-to-end bug fixes for OpenSpec workflows with TDD cycles.

1|1|Updated Apr 7, 2026
Search Tags:#workflow#tdd#debugging#traceability#openspec#bugfix
One-click install
npx skills add https://github.com/wonder-zhang/openspec-autodev --skill bugfix-wonder-zhang
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bugfix
Source: https://github.com/wonder-zhang/openspec-autodev/tree/main/skills/bugfix
Command: npx skills add https://github.com/wonder-zhang/openspec-autodev --skill bugfix-wonder-zhang

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The lightweight bug fix assistant for the OpenSpec + Superpowers workflow helps you diagnose and fix bugs quickly with minimal ceremony, maintaining OpenSpec traceability.

Core Features & Use Cases

  • End-to-end root-cause analysis guided by a deterministic four-step workflow (Information Gathering, Hypothesis, Verification, and Confirmation) to identify and document the bug.
  • Create a minimal OpenSpec record and change proposal, then apply a focused fix via a strict TDD cycle, all within a single agent workflow.
  • Branch Management and session-state tracking ensure reproducibility, audit trails, and easy rollback or continuation across sessions.

Quick Start

Describe the bug and start the fix workflow with the appropriate command to begin automatic analysis and patching.

Frequently Asked Questions about bugfix

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

FAQPage Schema
How do I automate end-to-end bug fixing with TDD and traceability?▼

Automated bug fixing with TDD and traceability uses a single-agent workflow to perform root-cause analysis, create OpenSpec records, run TDD cycles, and commit fixes. This ensures reproducibility and audit trails without manual intervention.

What is the best way to document a bug fix workflow for reproducibility?▼

Documenting a bug fix workflow for reproducibility involves creating minimal OpenSpec records and change proposals. Session-state tracking and persistent archives ensure you can audit, rollback, or continue the debugging process across sessions.

How does root-cause analysis work in an automated debugging workflow?▼

Root-cause analysis in automated debugging follows a deterministic four-step process: Information Gathering, Hypothesis, Verification, and Confirmation. This structured approach identifies, documents, and patches the bug within a strict TDD cycle.

Can I use a single-agent workflow for non-interactive bug patching?▼

Yes, single-agent workflows support non-interactive bug patching by applying strict TDD cycles and branch naming conventions like fix/<bug-slug>. Persistent session management with OpenSpec archives handles state automatically.

How do I manage branches and session state for OpenSpec bug fixes?▼

Managing branches and session state for OpenSpec bug fixes requires using fix/<bug-slug> naming conventions. Persistent session-state tracking with OpenSpec archives ensures reproducibility, easy rollback, and continuation across multiple debugging sessions.

What are the limitations of lightweight bug fixing workflows?▼

Lightweight bug fixing workflows are designed for single-agent debugging tasks. They apply focused fixes via strict TDD cycles with minimal ceremony, meaning they may not suit complex multi-agent coordination or deeply systemic architectural issues.

Related Skills

Explore More Software Engineering Skills→
udecodeudecode
434

browser-debug-setup

Set up a persistent Chrome debugging environment with a dedicated profile.

Official
Intermediate
RemseyMailjardRemseyMailjard

triage-issue

Investigate a reported bug and create a GitHub issue with a TDD fix plan.

Community
Intermediate
tiankong0101-bytetiankong0101-byte

superpowers

Enforce a spec-first workflow with brainstorming, TDD, debugging, and branch completion.

Community
Advanced
michael-harrismichael-harris
17

devteam-bug

Diagnose and fix software bugs through an interview-driven multi-agent workflow.

Community
Advanced