Home / Lessons / Judge the result / 14 of 27

Returning at the merge gate

I read the evidence, then decide what ships.

  1. Work reaches me as one pull request, with its evidence.
  2. Reviewed before it got here? One change, one story? Green on this exact commit?
  3. One of those is not true yet. It goes back.
  4. Your part: only you open the gate.
  5. Read the evidence, then decide what ships.

Review finishes before the work reaches me. One pull request tells one story I can trace. Changes that would make review unclear get separate pull requests.

The checks have to be green on the exact commit proposed for merge, not on an earlier one.

I do not replay every step the agents took. I review the evidence and decide.

Evidence pack
  1. Demand tile present
  2. Feasibility tile present
  3. Shows "Unavailable" when the provider refuses
  4. Plain wording, no raw query dump
  5. Marked groundable
  6. Marked sources scarce
  7. Advice line shown
  8. No internal file paths leaked
  9. No governance files leaked
  10. No country query leaked
  11. No keyword query leaked

PASS, 11 of 11 checks, 17 of 17 tests

Not done here: merge, production database changes.

Those two are mine.

From one real evidence pack. Every check passed. The last line says what was left for me.

How I do it

The real evidence pack shown on this site says it plainly: PASS, 11 of 11 checks, 17 of 17 tests, and "Not done here: merge, production database changes."

The rule

Make the thing you review small, single-purpose and tied to one exact commit.

The skill I use for this: /finishing-a-development-branch. Made by Jesse Vincent.

Read next

The ideas behind it

This lesson as plain text, for your agent. Or all 27 on one page.

Try “secrets”, “merge”, “handover” or “database”.