Find the commit that introduced a bug with git bisect
Prompt that plans a git bisect session with a reliable check, a good starting point and a clear reading of the result. Paste it into an AI tool of your choice, which then plans the git bisect session.
- Topic
- Apps & prototypes
- Type
- Prompt
- Level
- Intermediate
- Time
- about 10 min
Results depend on the tool, the model and what you enter.
Result preview
Example: written by our editors, not real AI output.
Check: ./check.sh → exit 0 = good, 1 = bad git bisect start git bisect bad HEAD git bisect good v2.3.0 git bisect run ./check.sh Does not build? → git bisect skip Result: a1b2c3d "Change date format in export" At the end: git bisect reset
Fill in
What you type stays in this browser window. We store and send nothing.
- a page renders wrongly
- a test fails since recently
- a calculation returns different numbers
- the app got slower
- an export is missing fields
- web app with a frontend build
- backend service
- library with tests
- mobile app
- monorepo with several packages
- an automated test exists
- a short script can check it
- only by clicking through by hand
- only with production-like data
- not sure yet
Your prompt
You have edited the prompt. Changes in the fields above no longer overwrite it.
This is an instruction for an AI, not the result itself.
Where this prompt works
These AI tools are a good fit for this prompt:
How to use it
- Fill in the fields or tap a suggestion. Leave out names, addresses and other personal data.
- Copy the finished prompt into an AI tool of your choice.
- Before you start, run the check once on the known good and once on the current version. If both give the same answer, the check is not yet reliable.
Why does this work?
Searching history by hand takes hours and often lands on the wrong commit. A bisect session halves the range with every step, but only works with a check that answers good or bad without doubt.
Tips
- Do not put credentials or real customer data into the check script; use test data.