bisect-regression
Find the exact commit that introduced a bug. Use when something worked before and broke, and you don't know which change did it.
来源信息
- 仓库
- Archive228/loopkit
- 最近来源活动
- 2026年6月29日 21:52
- 检测到的 SKILL.md 语言
- 英语
- 星标
- 757
- Forks
- 124
安装方式
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
检查来源文件
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
正在显示 SKILL.md
SKILL.md
来源说明 · 只读预览- name
- bisect-regression
- description
- Find the exact commit that introduced a bug. Use when something worked before and broke, and you don't know which change did it.
# Bisect the Regression
1. Find a known-good commit and a known-bad one. Confirm both by actually checking out and testing.
2. `git bisect start; git bisect bad <bad>; git bisect good <good>`.
3. At each step, run the SMALLEST test that distinguishes good from bad. Mark `git bisect good/bad`.
4. When git names the first bad commit, read its diff. The bug is in those lines — don't guess elsewhere.
5. `git bisect reset`. Report: the commit, the line, the one-sentence cause.
Automate it: `git bisect run ./repro.sh` if you have a script that exits non-zero on the bug.
在 GitHub 查看