Article · 2026-09-23

Fewer bad merges for one cheap check

Cheaper tokens made skipping review easier. Put a second reader on git push so a bad verdict blocks the merge.

The packaged push gate for this pattern: Nightforge Verify Gate CLI ($31.20). How the boundary works is below.

The labs cut prices. Writing got cheaper overnight.

Review did not get a matching discount. Same-session "looks good" still means the author wearing a different hat. You ask for a second opinion and you get the worker that wants to be done.

That is the hole cheaper tokens opened. Skipping the check got easier. The merge still needs a reader with no authorship memory.

Fewer bad merges for one cheap check

Move the second reader to the boundary you actually cross: git push.

A different session reads the diff. Its job is only to report what is wrong. A bad verdict blocks the push. Not "please reconsider." Block.

Writer does the smallest change that solves the ticket. Reviewer is read-only. You apply a fix or you do not. Then you push again.

If the hook can be shrugged off at 1am, it is still chat. A push that dies on a second model's no is a review.

What this is not

• Not a paste-the-diff security score in the browser.
• Not a catalog of who won the price war.
• Not rules files that change how the writer behaves. Rules change the agent that writes. They do not check the code after it is written.

(For wrong-file edits and rules-vs-enforcement, see the sister post: Stop Claude Code and Cursor from editing files you didn't ask for.)

Tonight on the next ticket

One scoped diff. Then push. If push has no second reader, you did not get a review. You got a chat.

Where Nightforge fits

Nightforge Verify Gate CLI ($31.20) is the independent verify gate before merge: a git pre-push hook and CLI, zero npm dependencies, Node 18+. It runs a second Claude pass on your diff against a six-failure-mode rubric and blocks on a bad verdict. The reviewer does not rewrite. You keep the merge button. The check is cheap. Fewer bad merges. Zip after Stripe.

You can also start with the free starter checklist, or pair rules that steer the writer (Master Config) with a post-diff score (Regression Risk Estimator) and a second-opinion prompt pack (Independent Reviewer). Rules change intent. The verify gate checks what actually landed.

This piece also ran as an X Article on @shipsatnight.