bugfix

Fixes keel project defects with test-first regression protection and structured bug logging.

Updated Jan 12, 2026
One-click install
npx skills add https://github.com/ab300819/keel-workflow --skill bugfix-ab300819
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bugfix
Source: https://github.com/ab300819/keel-workflow/tree/main/skills/bugfix
Command: npx skills add https://github.com/ab300819/keel-workflow --skill bugfix-ab300819

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Fixing bugs without a failing test first often leads to unverified fixes and recurring regressions. This Skill enforces a test-first bug repair workflow for keel projects, ensuring every fix is proven by a failing test, documented with root cause analysis, and protected by regression tests. ## Core Features & Use Cases - Test-First Repair Flow: Reproduce the bug with a failing test before touching code, then verify the fix by making the test pass. - Root Cause Diagnosis Gate: For unclear bugs, a structured hypothesis-and-falsification process prevents shotgun debugging. - Complexity Routing: Simple single-file bugs are fixed inline; complex multi-module bugs are escalated to /dev-tasks and /dev-workflow via sub-agents. - Bug Knowledge Base: Every fix is appended to docs/devdocs/05-bugfix-log.md with BUG-XXX numbering, severity, root cause, and linked regression test IDs. - Use Case: A user reports a login crash. The Skill locates the code, writes a failing test reproducing the crash, applies a minimal fix, runs the full suite, logs BUG-003 with root cause, and generates a conventional fix() commit. ## Quick Start Describe the bug you encountered and ask the assistant to run the bugfix workflow to reproduce, fix, and log it with a regression test.

Frequently Asked Questions about bugfix

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

FAQPage Schema
How do I fix a bug with regression test protection?

Run the bugfix workflow: it first writes a failing test that reproduces the bug, then applies a minimal code fix, and finally confirms the test passes along with the full suite. The fix is logged with a BUG-XXX ID and linked regression test number.

What is test-first bug fixing and why use it?

Test-first bug fixing means proving the bug exists with a failing test before changing any code. This guarantees the bug is actually reproduced, verifies the fix works, and leaves a permanent regression test preventing the bug from returning.

When should a bug be escalated to task decomposition instead of a simple fix?

Escalate to /dev-tasks when the bug spans multiple modules or files, the root cause is unclear after diagnosis, the fix may affect other features, or it requires multiple steps. Simple single-file bugs with known causes are fixed directly.

Can this workflow fix bugs in projects without keel documentation?

No, this Skill targets keel projects with numbered documentation. For non-keel projects, use the dev-flow skill instead. Baseline projects with 00-baseline.md are supported by tagging the related feature as 'baseline'.

What happens when a bug cannot be reproduced?

If the reproduction test passes, the bug is not confirmed and the workflow stops. It suggests verifying reproduction steps, checking recent commits that may have fixed it, and confirming environment details with the reporter.