fix-bug

仓库创建 2026年7月26日最近提交 20 小时前SkillHot 收录 16 小时前

这个 Skill 做什么

按流程修 bug：先读代码推测根因，写出能为该原因失败的测试，再改代码直到该测试和整个测试套件都通过。在修复回归、崩溃或“应该做 X 但做了 Y”的问题时使用，别一上来就随意改生产代码。优点是让修复有证据，避免治标不治本或引入新故障。

▸ 展开 SKILL.md 英文原文

The disciplined way to fix a bug: build a root-cause theory by reading the code, prove it with a test that fails for the right reason, then implement until that test goes green and the wider suite stays green. Load whenever the task is to fix a bug, defect, regression, crash, wrong output, or "it should do X but does Y" in existing code - before you start editing.

Stars

Forks

仓库内 Skill

积累中

7 日增星

安装 / 使用

给你的 Agent 一句话（通用）

帮我安装这个 skill：https://raw.githubusercontent.com/fagerbergj/dotagents/main/skills/fix-bug/SKILL.md

或 curl 直取 SKILL.md

curl -fsSL "https://raw.githubusercontent.com/fagerbergj/dotagents/main/skills/fix-bug/SKILL.md"

SKILL.MD 节选查看完整文件 ↗

# Fix a bug: theory → failing test → green

A bug fix is not "change code until the symptom goes away." That produces fixes that paper over the wrong cause, break something else, or silently stop working. The discipline below makes the fix *provably* address the real cause.

Do not edit production code until step 2 gives you a test that fails.

## The workflow

### 1. Build a root-cause theory by exploring the code

Read the actual code paths involved - `read_file`, `grep`, `git_log`/`git_diff` to see what recently changed. Trace how the input reaches the wrong output. State the theory in one sentence: *"X happens because Y, so Z is wrong."*

- A theory names a **specific mechanism**, not a

via SKILL·HOT · 数据来自 GitHub 公开信息 · 原文版权归作者所有