Release rollback
Agent-ready Markdown vault methodology with AGENTS.md, templates, skills, logs, and file-safe workflows.From the repository description
npx -y skills add dzhokhov/markdown-agent-vault --skill release-rollbackAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.6 KB, 322 tokens by cl100k_base, as published. Nobody here has run it
Release Rollback
Appointment
Make the release manageable and reversible: validate -> release decision -> rollback readiness.
Related context: LLM Rules].
Entrance
RELEASE_CHECKLIST.mdCHANGELOG.md- Current commit/branch/tag
$test-gates
Mode A: Release Readiness
- Check the
RELEASE_CHECKLIST.mditem by item. - Make sure there is a release version (
vMAJOR.MINOR.PATCH) and a recording inCHANGELOG.md. - Confirm the safe rollback point (last stable tag/commit).
- Prepare a short release decision packet for the owner.
Mode B: Incident Rollback
- Freeze's new rollouts.
- Find the last known good version.
- Choose the path of return (in descending cost):
- feature flag/config toggle off
git revertProblem Change- rollback to the previous stable tag
- Perform post-rollback smoke.
- Decide what new gate/test you need so it doesn’t happen again.
Tough rules.
- Do not issue a high-risk change without an explicit owner solution.
- Do not consider the release ready without rollback-path.
- In the conflict between speed and safety, choose reversibility.
Exit
Release status: GREEN|YELLOW|REDRollback readiness: READY|NOT_READYOwner action:Release | Hold | RollbackNext safest step:1 Specific Step
What ships with it: 5 files
1.2 KB alongside SKILL.md
agents/
- openai.yaml233 B
- README.md189 B
references/
- README.md205 B
- release-policy.md375 B
- README.md220 B