Agents screen pull requests so only qualifying changes ship.
What it solves: During a release freeze, in-scope pull requests are dispositioned against the admission standard, admitted ones merge after approval, and exceptions, a raised bar and CI readbacks re-derive decisions, reverting merged changes that no longer qualify.
How it runs
- Scope Section 1 of the standard sorts every open pull request against the release branch into in scope or out Who decides: The release manager confirms the scope
- Disposition Each in-scope pull request is admitted, deferred or rejected with a reason code Who decides: The release manager approves
- Merge and record Admitted pull requests are merged and each decision is recorded on the ClickUp board Who decides: The release manager approves each merge
- Exceptions A granted exception re-runs only that pull request, and its new reason code goes on the board Who decides: The release manager grants the exception
- Bar change Every in-scope pull request is re-derived, merged ones included, and merged non-admits get a revert and a revert card Who decides: The release manager approves every revert
- CI readback Pull requests named in the readback are re-derived under the bar in force now Who decides: The QA lead confirms the results and the release manager approves
- Closeout One summary per team group with admitted, deferred, rejected and reverted pull requests Who decides: The release manager approves the post
Tools it connects
- ClickUp: Carries the freeze board, one card per in-scope pull request with its reason code.
- GitHub: Holds the pull requests, their checks, the merges and the revert pull requests.
- Google Drive: Keeps the admission standard and every amendment to it.
- Slack (optional): Is where exceptions are requested, readbacks are posted and the group closeout is shared.
Set-up prompt
Paste this into Kylon, or start it in one click below.
Set up our release freeze triage desk in this Room. Take it one step at a time and wait for my OK before you move on.
1. Connect ClickUp, GitHub and Google Drive first, since the first run needs them. Tell me which ones still need connecting. Slack can wait until a step uses it.
2. Ask me who works this desk: the release manager, the QA lead and the engineering leads. Help me invite them to this Room.
3. Build a Freeze Board App with columns In Scope, Admitted, Deferred and Reverted, one card per in-scope pull request with its reason code.
4. Pull every open pull request against the release branch from GitHub and run each one through our scope check in Google Drive. Show me the in-scope list and flag anything triaged that looks out of scope.
5. For each in-scope pull request, propose a disposition and a reason code. If the bar has moved, re-derive every in-scope pull request including merged ones and propose a revert card for each merged pull request that no longer admits. Flag any decision whose reason code was updated in the thread but not on the Freeze Board.
6. Draft every merge, revert and board update for the release manager to approve in the thread before anything touches the release branch. Route each revert for a secondary check first. Route CI readbacks to re-derive under the bar in force now, then flag results for the QA lead to confirm.
7. Write our rules into this Room's guideline: scope is decided first under our checks, nothing merges or reverts until the release manager approves it in the thread, and CI readbacks get a secondary review.
8. After one clean freeze, offer to turn the closeout summary into an Automation.
Start with step 1. Once the tools are connected, or I say the rest can wait, ask me for our rules one at a time.