bug-fix-workflow

Automate reproducible bug-fix sessions to isolate, fix, verify, and record defects.

Updated Apr 9, 2026
One-click install
npx skills add https://github.com/ldmrepo/agent-harness --skill bug-fix-workflow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bug-fix-workflow
Source: https://github.com/ldmrepo/agent-harness/tree/main/template/.claude/skills/bug-fix-workflow
Command: npx skills add https://github.com/ldmrepo/agent-harness --skill bug-fix-workflow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It eliminates ad‑hoc, untracked bug‑fix attempts by providing a structured, bounded workflow that ensures bugs are reproduced, isolated, fixed, verified, and recorded reliably within the long‑running harness.

Core Features & Use Cases

  • Reproducible Fix Process: Guarantees the bug can be consistently recreated before any change.
  • Bounded Scope Enforcement: Keeps the fix limited to the specific issue, preventing accidental large‑scale refactors.
  • Automatic Artifact Updates: Updates task, issue, progress, and session summaries automatically.
  • Use Case Example: When a UI flow breaks after a recent change, the skill guides the coder agent through reproducing the failure, applying the minimal code change, adding regression tests, and updating the known‑issues registry.

Quick Start

Ask the coder agent to run the bug‑fix‑workflow skill on the current task, providing the relevant task and environment files.

Frequently Asked Questions about bug-fix-workflow

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

FAQPage Schema
How do I automate a reproducible bug fix workflow within a long-running agent?

Automating a reproducible bug fix workflow requires a structured agent harness that isolates, fixes, verifies, and records defects within a bounded scope to prevent untracked ad-hoc changes.

What is the best way to enforce bounded scope during automated debugging and regression fixes?

Enforcing bounded scope during debugging prevents accidental large-scale refactors by keeping the automated agent strictly limited to applying minimal code changes for the specific issue.

Do I need specific environment config and console commands to run an automated bugfix session?

Yes, running an automated bugfix session requires access to task files, environment config, and console commands such as bootstrap, smoke tests, unit tests, and issue tracking artifacts.

How does an automated agent update issue tracking artifacts and progress summaries after a bug fix?

An automated agent updates issue tracking artifacts by automatically modifying task, issue, progress, and session summary files upon successfully verifying the isolated defect and adding regression tests.

When should I not use a bounded bug-fix workflow for my coding agent?

You should not use a bounded bug-fix workflow for tasks requiring large-scale refactoring, feature development, or unbounded debugging sessions that fall outside the scope of isolated defect recovery.