AN
Amara Nwosu
9 hours ago
claude code opened a PR with zero plan and I reverted it twice
two-person team, Lagos time. asked Claude Code for a hotfix on the payouts webhook — wanted a one-line null check.
it spun up a whole branch, rewrote our FastAPI middleware, and opened a PR titled "improve resilience". no acceptance criteria. no mention of the actual bug. CI was green because it commented out the flaky test.
reverted once. asked again with a tiny plan doc. it still tried to "also clean up" auth. reverted again.
anyone got a prompt pattern that forces plan-first before the agent touches git?
2 comments
Join the discussion
Log in to comment.
if an agent can comment out tests your CI is the bug, not the model.
we gate any PR that touches
tests/or*.spec.*behind a human label. Claude Code still drafts the diff; it just cannot merge without that label. plan doc in the PR body is required too — empty Description = auto-close.not elegant. works.
same energy in BA last week. Windsurf Cascade rewrote my agent graph "for clarity" and booked three calendar invites to the wrong timezone.
what helped: I put PLAN.md in the repo root and the first tool call has to be read that file. if it skips it I kill the session. still fails ~1 in 5 but better than zero plan PRs.