bug-fixer

Diagnose and fix bugs through evidence-based root cause analysis and verified regression testing.

Updated Jul 3, 2026
One-click install
npx skills add https://github.com/LYGOLANG/fufan-cc-flow --skill bug-fixer-lygolang
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bug-fixer
Source: https://github.com/LYGOLANG/fufan-cc-flow/tree/main/.agents/skills/bug-fixer
Command: npx skills add https://github.com/LYGOLANG/fufan-cc-flow --skill bug-fixer-lygolang

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When users report errors, crashes, or broken functionality, ad-hoc guessing wastes time and often introduces new defects. This Skill enforces a systematic debugging discipline: collect evidence first, form ranked hypotheses, fix one issue at a time, and verify with compile and regression checks. ## Core Features & Use Cases - Evidence-Based Diagnosis: Gathers full stack traces, reproduction steps, environment info, and recent changes before forming any conclusion. - Hypothesis-Driven Fixing: Maintains at most 3 ranked hypotheses with explicit verification methods, fixing one logical point at a time and rolling back on failure. - Verified Repair Workflow: Every fix passes TypeScript compilation checks (tsc --noEmit), functional verification, and regression testing, with a stop-and-reassess rule after 3 consecutive failures. - Use Case: A user reports "the login page throws a 500 error after the latest deploy." The Skill collects logs and recent commits, identifies the most likely cause, applies a single targeted fix, verifies compilation and regression, then suggests a commit with a fix: prefix. ## Quick Start Tell the agent "this feature is broken" or paste the error message and stack trace, and it will systematically diagnose the root cause and fix it.

Frequently Asked Questions about bug-fixer

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

FAQPage Schema
How do I debug a reported bug systematically instead of guessing?▼

Collect complete evidence first: full error messages, stack traces, reproduction steps, environment details, and recent code changes. Then form at most three ranked hypotheses, verify the most likely one, and fix one logical point at a time with regression checks after each change.

How to fix a bug without breaking other functionality?▼

Change only one thing at a time and assess impact before editing. After each fix, run compilation checks such as tsc --noEmit, confirm the original bug no longer reproduces, and regression-test related features before moving on.

What should I do when the same bug keeps coming back after fixes?▼

Stop after three consecutive failed fix attempts and reassess. Repeated failure usually signals an architecture, environment, or understanding problem rather than a code-level issue, so re-examine your assumptions instead of patching again.

Why do mysterious bugs happen when a dev server is running?▼

Multiple running process instances are a common cause of strange bugs. When a bug involves service state, kill processes occupying the relevant ports first, then debug against a single clean instance.

When should I search the web before fixing an unfamiliar error?▼

Search first whenever the error message or library is unfamiliar. For third-party library bugs, check known issues and issue trackers before modifying your own code, since the root cause may be upstream.