bisect-regression

Sterne2

Forks0

Aktualisiert12. Juli 2026 um 12:09

Find the exact commit that introduced a bug. Use when something worked before and broke, and you don't know which change did it.

Installation

Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.

In Manus ausführen

Quelle

YaoYinYing

YaoYinYing/REvoDesign

GitHub-Repository öffnen Creator-Repositorys ansehen

Download

In Manus ausführen

Verwandte BerufeSOC

Basierend auf der SOC-Berufsklassifikation

SoftwareentwicklerInformatik- und Mathematikberufe·SOC 15-1252

SKILL.md

readonly

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

Find a known-good commit and a known-bad one. Confirm both by actually checking out and testing.
git bisect start; git bisect bad <bad>; git bisect good <good>.
At each step, run the SMALLEST test that distinguishes good from bad. Mark git bisect good/bad.
When git names the first bad commit, read its diff. The bug is in those lines — don't guess elsewhere.
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.

Mehr aus diesem Repository

gleiches Repository

adversarial-verify

YaoYinYing/REvoDesign

Review a diff against the goal spec assuming the code is BROKEN. The reviewer that lives in the maker's head always agrees with itself — this pulls review into a hostile, separate pass. Invoke after every code change before marking work done.

2026-07-122

authz-check

YaoYinYing/REvoDesign

Verify that an endpoint checks ownership, not just authentication. Use on any handler that reads or mutates user data.

2026-07-122

changelog-from-diff

YaoYinYing/REvoDesign

Turn a set of commits or a diff into a clean, user-facing changelog entry. Use before a release or PR description.

2026-07-122

clean-commits

YaoYinYing/REvoDesign

Turn messy WIP into clean, atomic commits with messages that explain why. Use before opening a PR.

2026-07-122

context-budget

YaoYinYing/REvoDesign

Keep the agent's context lean so accuracy doesn't collapse. Use on long sessions, big files, or when the agent starts hallucinating.

2026-07-122

design-system

YaoYinYing/REvoDesign

Make frontend output look intentional, not AI-generated. Use for any UI work — components, pages, layouts.

2026-07-122

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

Find a known-good commit and a known-bad one. Confirm both by actually checking out and testing.
git bisect start; git bisect bad <bad>; git bisect good <good>.
At each step, run the SMALLEST test that distinguishes good from bad. Mark git bisect good/bad.
When git names the first bad commit, read its diff. The bug is in those lines — don't guess elsewhere.
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.