Bisect predicate that classifies commits reliably

What you fill in

• Script environment[shell]ExamplePOSIX shell
• Failure signature[bug_brief]ExampleBuild with npm test; bad commits return duplicate invoice IDs for the supplied fixture

How to use it

1. 1Open it in PromptVault. Find it in Coding, or search for “Bisect predicate that classifies commits reliably”.
2. 2Fill in the 2 blanks. script environment and failure signature — the only things the prompt cannot know.
3. 3Copy and paste it into Cursor. It also works with GitHub Copilot and Ollama.

About this prompt

“Bisect predicate that classifies commits reliably” is a intermediate coding prompt. For engineers turning a bug signature into an executable Git bisect check. It is 66 words long and written to get a usable answer on the first message, in Cursor, GitHub Copilot and Ollama or any other chat assistant. Good for: git, automation, debugging, troubleshooting and first draft. Like every prompt in PromptVault, it was written and edited in-house, and it works offline once the app is installed.