safe-rollout
Skill0 starsChanged 4 months agoMITView on GitHub
Use when shipping a risky or wide-reaching change (data migration, shared-component change, behaviour swap) that needs to go out gradually with a rollback path. Produces a phased rollout plan behind a flag.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- Mehul72/skillstheir own version, first seen Nov 8, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- Mehul72/skills★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository6 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- commitSkill
- improve-skillSkill
- pr-descriptionSkill
- scaffold-moduleSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 26
Define rollback: before enabling: flipping the flag off must fully restore the old behaviour, with no data left in a bad state.
- Distinctive: line 35
Leave a flag and dead code path lingering after 100% — clean it up.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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
Safe Rollout
Overview
For changes that could break many call sites or users, ship behind a flag and roll out in phases with a clear rollback at every step. Never flip a risky change on for everyone in one commit.
Workflow
- Assess blast radius — list every caller / surface the change touches. If it needs strong cross-entity consistency, keep it in one unit rather than spreading it.
- Gate behind a flag — default OFF. Old path stays byte-identical when the flag is off (document this in a backwards-compatibility note).
- Phase the rollout:
- Internal / staging only.
- Small percentage of production.
- Ramp up while watching metrics.
- 100%, then remove the flag and dead path in a follow-up.
- Define rollback before enabling: flipping the flag off must fully restore the old behaviour, with no data left in a bad state.
- Watch — name the metrics/logs that tell you it's working (error rate, latency, the specific user outcome).
Do not
- Enable a risky change globally in one step.
- Ship without a documented, tested rollback.
- Leave a flag and dead code path lingering after 100% — clean it up.
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.