rollback
Skill0 starsChanged 46 days agoMITView on GitHub
Revert a bad change or roll back a deployment — the risk-reducing counterpart to /ship. Fast-path but still gated by tests.
- Commits and pushes
11 other projects use a version of this.
Adopted by
Most recently taken up by
- FAHTHIZ/oasistheir own version, first seen Nov 16, 2026
- elfrost/ai-patchlabtheir own version, first seen Nov 9, 2026
- synaptiai/agent-capability-standardtheir own version, first seen Nov 1, 2026
- harshanandak/forge-legacytheir own version, first seen Oct 17, 2026
- tejastn10/workbenchtheir own version, first seen Oct 13, 2026
- purpleeddy/claddingtheir own version, first seen Oct 11, 2026
Used with
Projects with it also use status.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
AnthropicSkillstatus
Case status summary by audience — client-facing (plain language), internal (for the professor), or court-ready (formal caption format per local rules). Same facts, different framing and depth. Use when a student needs to update the client, brief the professor, or prepare a court status report.
Also in 3 projects that use this
Other versions11 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 11
- suboss87/FDEOps★ 940same name
- popup-studio-ai/bkit-claude-code★ 605same name
- ww-w-ai/bkit-claude-code★ 605same name
- ww-w-ai/bkit-gemini★ 66same name
- nahid-sparktales/agent-dispatcher★ 59same name
- purpleeddy/cladding★ 16same name
- synaptiai/agent-capability-standard★ 7same name
- FAHTHIZ/oasis★ 4same name
- harshanandak/forge-legacy★ 4same name
- elfrost/ai-patchlab★ 2same name
1 more not listed
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 repository29 other files it gives its agents.
- hosts/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- adrSkill
- api-designSkill
- auditSkill
- code-reviewSkill
- concurrency-performanceSkill
- coverageSkill
- debuggingSkill
- debugSkill
- fast-laneSkill
- fixSkill
- implementSkill
- intakeSkill
- leanSkill
- migration-safetySkill
- nonnaSkill
- observabilitySkill
- planSkill
- refactoringSkill
- releaseSkill
- reviewSkill
- security-reviewSkill
- shipSkill
- supply-chainSkill
- syncSkill
- tddSkill
- tdd-workflowSkill
- testSkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 1 is distinctive, and 2 are very specific to this project.
0
Common
Most of the 10 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- could be automatic: a setting could enforce it
- Very specific: line 23
Create the revert: Use git revert <hash> --no-edit (one commit) or git revert <oldest>..<newest> --no-edit (a range).
- Distinctive: line 26
Reconcile the external system: If the bad change reached production (a deploy, a migration, a published package), confirm the live system …
- Very specific: line 27
Sync: Update docs/STATUS.md, move the tracker issue, run /sync.
“Common” is measured: kept by at least 6 in 10 of the 10 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
!git log --oneline -20 !git status --short
Rollback: $ARGUMENTS
Safety posture
Rollback is risk-reducing — it narrows blast radius, so it may be expedited. But "expedited" does not mean "untested": the revert still passes the gate before it ships. The external system is the source of truth — reconcile actual state before declaring success (see .claude/rules/safety.md).
Steps
- Identify the target. From the
git logabove, pinpoint the offending commit(s) or the PR range to revert. State in one sentence: reverting X because Y. - Check current state. Confirm what is live (branch, last deploy, any in-flight PRs touching the same surface). Do not revert a commit that has already been superseded.
- Create the revert. Use
git revert <hash> --no-edit(one commit) orgit revert <oldest>..<newest> --no-edit(a range). Do notreset --hardor force-push unless the change has not yet reacheddevelop/mainand you have explicit authorization. - Run the gate.
/test— the suite must be green on the revert branch. A revert that breaks tests is not safe to ship. - Fast-path PR. Open a PR to
develop(ormainif the bad commit is already there and a hotfix path is approved). Label itrollback. Link the original PR/issue. - Reconcile the external system. If the bad change reached production (a deploy, a migration, a published package), confirm the live system reflects the intended state — don't assume the revert is sufficient without checking. Halt on unexplained divergence.
- Sync. Update
docs/STATUS.md, move the tracker issue, run/sync.
Output
The revert commit(s), the PR link, gate result, and a one-line confirmation that the external system state is reconciled.
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.

