bisect-regression

Étoiles2

Forks0

Mis à jour12 juillet 2026 à 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

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Exécuter dans Manus

Source

YaoYinYing

YaoYinYing/REvoDesign

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Exécuter dans Manus

Métiers associésSOC

Basé sur la classification professionnelle SOC

Développeurs de logicielsProfessions informatiques et mathématiques·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.

Plus depuis ce dépôt

même dépôt

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.