Finding the bad commit with GPT-6 Astra and 10 GitHub repos

Marlen @MarlenuiiOriginally posted 2026.10.25

Open original on X

AI agents are getting f...cking illegal GPT 6 Astra and Claude Code can find the exact commit that broke your entire application 10 GitHub repos for finding regressions, tracing broken code, fixing bugs, and verifying patches automatically FIND THE BAD COMMIT 01 Git https://github.com/git/git → use git bisect to locate the first broken commit without inspecting every change 02 Delta https://github.com/dandavison/delta → inspect syntax highlighted diffs and understand exactly what changed 03 git-filter-repo https://github.com/newren/git-filter-repo → analyze and rewrite repository history when deeper cleanup is needed TRACE THE ROOT CAUSE 04 ast-grep https://github.com/ast-grep/ast-grep → search for structural code patterns across the repository 05 Semgrep https://github.com/semgrep/semgrep → detect risky patterns and investigate affected code paths 06 CodeQL https://github.com/github/codeql → analyze data flows and identify potentially vulnerable code paths REPRODUCE THE FAILURE 07 Playwright https://github.com/microsoft/playwright → reproduce browser regressions with automated tests 08 Vitest https://github.com/vitest-dev/vitest → run fast regression tests for JavaScript and TypeScript VERIFY THE PATCH 09 StrykerJS https://github.com/stryker-mutator/stryker-js → test whether your regression tests catch deliberate code mutations 10 Reviewdog https://github.com/reviewdog/reviewdog → surface automated findings directly in code reviews THE WORKFLOW WORTH SAVING 32 suspicious commits Only about 5 checks needed with binary search Instead of reading every diff, let Git repeatedly test the midpoint git bisect start git bisect bad HEAD git bisect good <known-good-commit> git bisect run ./test-regression.sh git bisect reset COPY THIS INTO GPT 6 ASTRA OR CLAUDE CODE " Find the regression using git bisect and a deterministic testEstablish a known good commit and a reproducible failing testIdentify the first bad commitInspect the diff and explain the root causePropose the smallest possible fixAdd a regression test and verify the resultNever claim success without passing tests " the architecture: broken build → reproduce → bisect → isolate commit → inspect diff → patch → regression test → verify Most developers ask AI to guess why their code broke A better workflow makes AI prove exactly when the bug appeared 32 commits → 5 checks → 1 culprit Save this before your next production regression

This post quotes another post: x.com/marlenuii/status/2109673372091126158