Release Gates for Agent-Generated Code

About this workflow

Put agent output through a real merge gate: automated review, tests, security scans, and human sign-off proportional to risk.

What happens when you run it

1. 1
   Stack the deterministic and test-based checks first.

   Runs flow-release-gates-agent-generated-code-1-assemble-the-automated-gate on Claude Sonnet 4.6
2. 2
   Not all changes deserve the same gate - risk sets the depth.

   Runs flow-release-gates-agent-generated-code-2-classify-change-risk on Claude Sonnet 4.6
3. 3
   Reviewers must know it is agent code, and risky code needs a human name on it.

   Runs flow-release-gates-agent-generated-code-3-label-provenance-and-require-sign-off on Claude Sonnet 4.6
4. 4
   The gate must be auditable and calibrated over time.

   Runs flow-release-gates-agent-generated-code-4-record-audit-and-tune on Claude Sonnet 4.6

Best for

• •Recurring tasks you currently copy-paste between tools.
• •When a single prompt isn't enough — you need a chain where output(n) feeds prompt(n+1).
• •Fork and adapt if your inputs differ materially from the author's use case.

Models used