Home / Lessons / Judge the result / 20 of 27

Nobody grades their own homework

A builder's report that it is done is a claim. Someone else decides if it is true.

  1. The builder says it is done. That is a claim, not proof.
  2. If the builder checks its own work, it passes. Nobody looked.
  3. So someone who did not build it does the checking.
  4. A false claim is sent back.
  5. A true one goes on to the gate, with evidence.

Builders never approve their own work. Independent checks look at three things: the diff, how the code behaves when it runs, and what the user experiences.

Different reviewers look for different things. One for defects in the code. One for security, structure and how easy it will be to maintain. One for dangerous paths and leaked secrets. One that walks the user journey in a real browser.

How I do it

I use Bugbot for code defects on the complete branch, Thermos for security, structure and maintainability, a vulnerability scanner for dangerous paths and secret leaks, and Gstack for browser checks of the user journey. Those names are my setup today. The rule does not depend on them.

The rule

Use review that the builder does not control, and make it look at the running product.

The skills I use for this: /browse, /review-bugbot, /thermos. Made by Garry Tan and Cursor.

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”.