revert-change
Skill0 starsChanged 18 days agoMITView on GitHub
Safely undo a commit, merge, PR, or deploy without rewriting shared history. Use when the user asks to revert, roll back, undo a merge, or back out a change. Do not reset shared branches.
1 other project uses a version of this, 1 of them edited.
Adopted by
Most recently taken up by
- rpraharaj/ai-engineeredited, first seen Nov 1, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 1
- rpraharaj/ai-engineer★ 113% same
Wrote their own version · 0
None found.
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 repository66 other files it gives its agents.
- AGENTS.mdAGENTS.md
- a11y-passSkill
- assess-changeSkill
- build-regression-packSkill
- charter-exploratorySkill
- classify-dataSkill
- commitSkill
- cut-releaseSkill
- data-changeSkill
- debugSkill
- design-experimentSkill
- diff-environmentsSkill
- draft-steercoSkill
- engineering-barSkill
- explain-codeSkill
- explore-codebaseSkill
- fix-ciSkill
- handoffSkill
- implement-changeSkill
- incident-triageSkill
- lean-reviewSkill
- map-dependenciesSkill
- map-design-handoffSkill
- map-processSkill
- open-prSkill
- performanceSkill
- plan-data-migrationSkill
- plan-incrementSkill
- plan-rollbackSkill
- plan-uatSkill
- prioritize-backlogSkill
- production-passSkill
- ready-to-mergeSkill
- record-decisionSkill
- refactor-safelySkill
- review-architectureSkill
- review-changeSkill
- review-pipelineSkill
- security-passSkill
- shape-workSkill
- ship-notesSkill
- spec-analyticsSkill
- spec-observabilitySkill
- start-projectSkill
- synthesize-discoverySkill
- triage-blockersSkill
- triage-defectSkill
- update-raidSkill
- verify-uiSkill
- write-api-examplesSkill
- write-architectureSkill
- write-designSkill
- write-dev-tasksSkill
- write-docsSkill
- write-integration-contractSkill
- write-nfrSkill
- write-opportunitySkill
- write-prdSkill
- write-requirementsSkill
- write-runbookSkill
- The first 60 shown.
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 32
If you cannot name the target, stop.
- Distinctive: line 45
Run AGENTS.md Test if cheap.
≈ “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
Revert change
Undo a known change. Prefer a new revert commit. Do not reset --hard or force-push a branch other people use.
Is this the right skill?
| Signal | Do this instead |
| Live incident, action not yet chosen | incident-triage first |
| Spoken rollback plan for a release | plan-rollback then this if git undo is the step |
| Not a git repo | stop |
Required inputs
- Exact target: commit SHA, merge, PR/MR, tag, or release
git- For a deployed target:
context/environments.md,context/decision-rights.md, and the named rollback plan; missing authority or environment → stop before runtime changes
If you cannot name the target, stop.
Human decisions (do not invent)
reset --hard(only if they asked to discard, local branch, unpushed)- Push (only if asked; never force to default branch)
Procedure
- Identify the target (
git log,status, current branch). - Shared/pushed/merge →
git revert(-m 1on a merge). Default branch → revert only, never reset. Unpushed local commits on your branch → reset only as they asked. - Deploy already out: identify the exact deployed revision and environment before any runtime action. Use the existing rollback plan and verify authorized human evidence using
context/decision-rights.md. A git revert does not authorize production rollback. If policy reserves production execution for a human, hand off the reviewed command; otherwise run only the explicitly approved existing rollback. Unknown or stale authority → stop. If no rollback path exists, say what a human must decide. - Secret files: a revert must not restore committed secrets without telling the user.
- Run
AGENTS.mdTest if cheap. If this stopped a fire, a focused check is enough — say what you did not run.
Output
- Path: the revert commit (or local reset)
- Template: references/revert-report.md
Quality bar
- Target named
- Shared history not rewritten
- No force to main/master/trunk
- Runtime rollback has current target/environment approval evidence and respects the production execution policy
Done
Fill the report. Do not push unless asked.
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.