What problem does it solve? It prevents hasty, unverified code changes by enforcing a disciplined bug-fixing workflow: analyze first, locate the root cause, confirm the diff with the user before editing, verify with regression tests, and archive a reusable fix summary. ## Core Features & Use Cases - Phased Workflow: Ten phases from historical conversation review, decomposition, root cause location, and solution design through implementation, environment refresh, regression testing, and summary. - Mandatory Confirmation Gate: Before any code change, presents the root cause, fix plan, and a diff preview, requiring explicit user approval. - Automatic Archival & Git Handling: Writes a structured fix report (including prevention advice) to a configurable docs directory, detects the docs Git repository, and separately handles doc commits versus code commits. - Use Case: A user reports a null-pointer error in an API service; the skill traces the call chain, identifies the missing null check, shows the diff for approval, applies the fix, restarts the affected container, reruns the failing scenario, and archives the report. ## Quick Start Start your message with "bugfix: " followed by a description of the problem, including the error message, reproduction steps, and expected behavior.