Skip to content
Skills Library
Programming · Automation

undo

/undo

Put the workspace's main copy back to an earlier safe point (D80). Use when the user says "undo", "go back to yesterday", "put it back how it was", "something broke since Tuesday", or asks what safe points exist. Never a force-push and nothing is deleted: the undo is a new step on top, and can itself be undone.

Licence
Apache-2.0
Last repository change
09.11.2026

Assessment and security

86/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content21 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 09.11.2026, without references to retired models or APIs.

Licence

Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.

What it does and when to use it

Put the workspace's main copy back to an earlier safe point (D80). Use when the user says "undo", "go back to yesterday", "put it back how it was", "something broke since Tuesday", or asks what safe points exist. Never a force-push and nothing is deleted: the undo is a new step on top, and can itself be undone.

Triggers from the description

undogo back to yesterdayput it back how it wassomething broke since Tuesday
Original author description

Put the workspace's main copy back to an earlier safe point (D80). Use when the user says "undo", "go back to yesterday", "put it back how it was", "something broke since Tuesday", or asks what safe points exist. Never a force-push and nothing is deleted: the undo is a new step on top, and can itself be undone.

How it works

SKILL.md has no level-two headings · 29 lines, 254 words

SKILL.md preview
---
name: undo
description: >
  Put the workspace's main copy back to an earlier safe point (D80). Use when
  the user says "undo", "go back to yesterday", "put it back how it was",
  "something broke since Tuesday", or asks what safe points exist. Never a
  force-push and nothing is deleted: the undo is a new step on top, and can
  itself be undone.
---

# Undo

The caretaker leaves a safe point (a tag called `safe/YYYY-MM-DD`) on the
GitHub backup every morning and keeps 30 days of them. `kit undo` restores the
main copy to one of them as a new commit, so nothing since is lost from
history, only moved out of the way.

Say first: "I can put everything back to how it was on any morning in the
last 30 days. Nothing gets deleted; it's one more step on top that we can
undo too."

1. `kit undo list` shows the safe points and which one main is at now. Read
   the dates out in plain words ("this morning", "yesterday", "last Tuesday").
2. Ask which one. Only a clear answer moves on.
3. If `kit land` would find unsaved changes, land them first (the user's
   current work is kept in history too).
4. `kit undo --to safe/<date>`. Read the JSON:
   - `via: main`: done. Say "The main copy is back to <day>. What changed
     since is still kept, so say 'undo the undo' if you change your mind."
   - `via: pull_request`: a lock on main asked for a pull request. Say "Put
     it back as finished work; the caretaker checks it and brings it in, in
     about an hour." Nothing more to do.
   - `reason: main already matches`: say so.
5. `kit sync --at end` so the local copy matches.

Never run git commands to do any of this by hand; the guard blocks them for
a reason (tags and history are the recovery net).

Versions

RepositoryScoreLicence
This page · kriegcloud/beep-beginners86Apache-2.0
thettwe/nyann100MIT
atakanelik34/bilinc-memory-history96MIT
librosdeia/builder-method-claude-plugin90MIT
KROU4/claude-kaizen86MIT

Database snapshot: 13.11.2026 · package version f7541724b320 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 91commit-push
    Commit with a Conventional Commits subject, then push. Use for /commit-push, "commit and push", "commit this and push". Must push. Never force-push.
  • 87undo-bootstrap
    Reverse a bootstrap or retrofit run by walking its BootRecord manifest: restore pre-state files, drop branches that were created, surface anything that couldn't be safely undone. TRIGGER when the user says "undo the bootstrap", "undo nyann setup", "revert nyann setup",…
  • 90restore
    Undo the founder's OS back to an earlier saved version, non-destructively, wrapping git so they never type a git command. Trigger on "undo", "undo to before this morning", "restore to yesterday", "roll back", "go back to last week", "revert my changes", or any plain request to…
  • 100git-undo-recovery
    Recover from a git mistake - lost commits after `reset --hard`, a deleted branch, a commit made on the wrong branch, a bad merge or rebase, a dropped stash, a force-push that overwrote someone's work, files lost to `checkout .`, `restore` or `clean`. Use this whenever the user…
  • 85undo-mistake
    Safely undo git mistakes - discard uncommitted edits, unstage files, fix the last commit, recover from committing on the default branch or a teammate's branch - without force-pushing. Use when someone says "undo", "I messed up", "wrong branch", or "committed something by accident".
  • 100git-safe-history-rewrite
    Rewrite git history without losing work or clobbering other people - amend, reset, squash, reorder, drop or edit commits, change a commit message, remove a commit from a branch, or force-push. Use this whenever the user asks to amend, squash, fixup, "undo the last commit", "get…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.