bugfix

Guides structured bug fixing through root cause analysis, confirmed diffs, verification, and archival.

Updated Aug 1, 2026
One-click install
npx skills add https://github.com/lov-b/Skills --skill bugfix-lov-b
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bugfix
Source: https://github.com/lov-b/Skills/tree/main/skills/bugfix
Command: npx skills add https://github.com/lov-b/Skills --skill bugfix-lov-b

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

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 a structured debugging workflow?

Start your message with "bugfix:" followed by the symptoms, reproduction steps, and expected behavior. The workflow decomposes the issue, locates the root cause with evidence, and only edits code after you approve a diff preview.

How does the bugfix skill confirm changes before editing code?

Before implementation it presents the root cause summary, the chosen fix plan, and a diff preview of affected files. You explicitly choose to apply the fix, adjust the plan, or skip changes, so no code is modified without approval.

Can the bugfix workflow span multiple conversation turns?

Yes. Analysis phases can extend across multiple turns while a checklist tracks progress. When you return to the same bug, the workflow resumes from the last completed phase instead of restarting, unless the environment or code has changed.

Where are bug fix summary reports saved?

Reports are saved to a user-specified path, a configured defaultSaveDir in the user-level config.json, the project's docs/bugfix directory, or the system Downloads folder as a fallback. Filenames follow the pattern bugfix-{timestamp}-{title}.md.

What happens if the remote Git push fails after a fix?

The local commit is kept and the push is skipped without rollback. The failure reason is reported in the fix summary, and the bug is still considered fixed since push failure does not affect the verified code change.