Home / Lessons / Judge the result / 14 of 27
Returning at the merge gate
I read the evidence, then decide what ships.
- Work reaches me as one pull request, with its evidence.
- Reviewed before it got here? One change, one story? Green on this exact commit?
- One of those is not true yet. It goes back.
- Your part: only you open the gate.
- 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.
- Demand tile present
- Feasibility tile present
- Shows "Unavailable" when the provider refuses
- Plain wording, no raw query dump
- Marked groundable
- Marked sources scarce
- Advice line shown
- No internal file paths leaked
- No governance files leaked
- No country query leaked
- No keyword query leaked
PASS, 11 of 11 checks, 17 of 17 tests
Not done here: merge, production database changes.
Those two are mine.
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.
Rule 14. Make the thing you review small, single-purpose and tied to one exact commit. (Returning at the merge gate, https://chiefofagents.si/one-page#rule-14)
The skill I use for this: /finishing-a-development-branch. Made by Jesse Vincent.
Read next
The ideas behind it
- What is a human gate?A protected action that cannot go ahead until an authorised person approves it.
- What is an evidence pack?The test results, review findings, screenshots, logs and state needed to judge a claim that work is complete.
This lesson as plain text, for your agent. Or all 27 on one page.