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.