القائمة
Find the exact commit that introduced a bug. Use when something worked before and broke, and you don't know which change did it.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| 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. |
git bisect start; git bisect bad <bad>; git bisect good <good>.git bisect good/bad.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.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.
Verify that an endpoint checks ownership, not just authentication. Use on any handler that reads or mutates user data.
Turn a set of commits or a diff into a clean, user-facing changelog entry. Use before a release or PR description.
Turn messy WIP into clean, atomic commits with messages that explain why. Use before opening a PR.
Keep the agent's context lean so accuracy doesn't collapse. Use on long sessions, big files, or when the agent starts hallucinating.
Make frontend output look intentional, not AI-generated. Use for any UI work — components, pages, layouts.