git-snapshot-rollback

Original：🇨🇳 Chinese

Translated

1 scripts

Used in Git development when you need to abandon current attempts and roll back to a historical commit. It automatically archives the current state to the archive/ branch and establishes bidirectional links (source and target) in ARCHIVE.md to ensure traceability of the development decision flow. Suitable for scenarios requiring safe rollback while retaining the context of failed attempts.

3installs

Sourcecafe3310/public-agent-skills

Added on2026-05-16

NPX Install

npx skill4agent add cafe3310/public-agent-skills git-snapshot-rollback

SKILL.md Content (Chinese)

View Translation Comparison →

Git Snapshot & Rollback

This skill ensures that when rolling back Git commits, not only are current attempts (Snapshot) retained, but also a traceable decision chain is built through

ARCHIVE.md

via automated scripts.

Core Workflow

1. Confirm Rollback Target

Obtain the target Commit Hash that the user wants to roll back to.
Ask or summarize the specific reason for the rollback.

2. Execute Automated Rollback Script

Before execution, you must ask the user whether to push the archive branch to the remote repository.

Use

run_shell_command

to call the skill's built-in script:

If the user agrees to push:

python3 <path_to_skill>/scripts/rollback.py <Target_Commit> "<Reason>" --push

If the user disagrees with pushing (default):

python3 <path_to_skill>/scripts/rollback.py <Target_Commit> "<Reason>"

The script will automatically complete the following:
1. Commit all uncommitted changes.
2. Create the
```
archive/{current_branch}/YYYY-MM-DD-HH-mm
```
  branch.
3. Update the
```
ARCHIVE.md
```
  record in the archive branch.
4. (Optional) Push the archive branch to the remote.
5. Return to the original branch and execute
```
git reset --hard
```
  .
6. Update
```
ARCHIVE.md
```
  in the original branch and commit the rollback record.
7. List all branches that are currently ahead of the remote (unpushed).

3. Result Verification

Check whether
```
ARCHIVE.md
```
has correctly recorded the bidirectional links for this rollback.
Confirm that the current branch is in the target Commit state.

Recording Specifications

For the specific format of
```
ARCHIVE.md
```
, please refer to references/log-format.md.
The Commit Message for each rollback must include information about the source archive branch.

Usage Prohibitions

It is strictly forbidden to directly execute
```
git reset --hard
```
to discard a large amount of work without using this skill.
Do not modify or delete historical records in
```
ARCHIVE.md
```
.