Assemble the automated gate

Stack the deterministic and test-based checks first.

First time here? Paste the Context Pack first so the AI understands your project - open it from the header above.

Prompt Capsule

Build the automated portion of the gate for agent-generated changes. Compose the layers already available (or build the missing ones): the rule-file review gate (deterministic policy checks on the diff), the full test suite plus the verification evidence the agent produced, security scans (the injection/red-team suite where the change touches agent behavior; SAST where applicable), dependency/supply-chain checks for any new deps, and a secret scan on the diff. Wire these as required status checks on the change (PR or equivalent). Any failure blocks. Ensure these run on agent changes at parity with or above human-change checks. Test by pushing an agent change with a planted rule violation and a failing test and confirming both block the merge.

Paste into EmergentFull Build: complete implementation prompt with explicit requirements

Quick is short. Full Build is recommended for most steps. Strict forces real logic when the AI keeps faking output.

Actual change check

Expected after this step

A stacked automated gate blocking on any failed check.

Should NOT happen

An existing feature broke
A button only logs to console
Data disappears after refresh
Errors fail silently with no visible state

This is what should exist before you continue. If reality does not match, do not move on.

Your notes for this step

Track what changed, failed, or needs follow-up. Notes export with the flow.

Pass the Verify Gate to complete this step

Verify before continuing

Do not move on until every check is true. The complete button stays locked until then.

Rules, tests, security, deps, and secrets all gateParity-or-stricter versus human-change checksPlanted failures block as expected

Do not continue if…

! Auto-merging agent PRs on green CI with no human ever looking at risky ones
! Applying weaker checks to agent code than to human code
! No risk tiering, so a typo fix and a payment change get identical review
! Unlabeled agent changes, so reviewers do not know to look harder

If the AI messes this up

Use this when:

- it only made visual forms or placeholder UI
- buttons do nothing or only log to console
- data is not persisted - state disappears on refresh
- something that worked before is now broken

Use this when the AI fakes progress or breaks the feature. It forces a real fix.

An agent change merged on partial checks. Make every layer a required status check (not advisory) and confirm the merge is technically blocked until all are green - advisory checks get ignored under deadline.