release-schedule
Skill0 starsChanged 2 months agoMITView on GitHub
Book a change window for one pull request from a person's phrase ("in 2h", "tomorrow 09:00") when the estate has a calendar. Use when asked to schedule a release, reserve a slot, or say when a change will go. It books one window; it never claims the berth, never deploys, never rebooks a lapsed window.
In this repository8 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- change-activateSkill
- change-requestSkill
- change-settleSkill
- change-watchSkill
- release-endSkill
- release-startSkill
- standard-changeSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 19
Run ./change/reap.sh first: next-available appends behind dead windows (024 F9).
- Distinctive: line 26
No open window overlaps on this environment (exit 5).
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
/release-schedule [PR] [when]
The scheduled case: a calendar in front of the berth. Reserving is not deploying; when the window opens the guards run again (five-properties P2; experiment 003).
Calls ./change/schedule.sh block <pr> "<groups>" <minutes> --at <iso>.
The time comes from ./change/when.sh "<phrase>": schedule.sh accepts only
ISO 8601 UTC and must not learn the phrases. Groups come from
./change/groups.sh <pr>.
Preconditions, checked before calling
- Run
./change/reap.shfirst: next-available appends behind dead windows (024 F9). - The PR is OPEN. block refuses MERGED and CLOSED with exit 2; say it first.
- Groups is non-empty. With none, the word is
release:skip. - The time is in the future. when.sh refuses what it cannot read; do not guess.
- The duration is at or above the floor: 3 + soak + apps - 1, plus 10 for a
control-plane change (exit 6). Never pass
--short. - No open window overlaps on this environment (exit 5).
- This PR holds no open window already:
./change/schedule.sh windows <pr>. block does not check this and 024 F9 left one change holding two.
The one thing it writes
One window row in refs/idp/schedule, by compare-and-swap. block also adds
release:scheduled today; under #125 that is the pipeline's record and stays
the pipeline's.
What it refuses, and says
- "#N is MERGED; a landed change needs no window."
- "In the past; now is T."
- "20m cannot hold this change; it needs 34m (deploy+settle 3, soak 5, +1 per extra app, +10 control-plane)."
- "staging is booked by CHG-... over S..E; next free slot is T."
- "#N already holds CHG-...; unschedule it first."
- And what block does not say: "booked into S..E; the quantum is 30m so 20m became 30m" (024 F9: silent rounding).
What it never does
Claim the berth; add the start label or deploy:staging; book production
(CHANGE_ENV stays staging); rebook after a lapse (a person's act,
reap.sh); touch the class, the approval, or any observation.
How the person knows
block prints the id and S..E; release:scheduled appears; this skill posts
the one comment block does not: the window id, and that reserving is not
deploying and the guards run again when it opens.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

