git-snapshot-rollback

Archive current Git state and reset to a target commit.

248|30|Updated Feb 18, 2026
One-click install
npx skills add https://github.com/cafe3310/public-agent-skills --skill git-snapshot-rollback
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-snapshot-rollback
Source: https://github.com/cafe3310/public-agent-skills/tree/main/skills/git-snapshot-rollback
Command: npx skills add https://github.com/cafe3310/public-agent-skills --skill git-snapshot-rollback

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill prevents destructive Git rollbacks from losing valuable work by creating traceable snapshots and recording the reasoning behind recovery operations.

Core Features & Use Cases

  • Safe Rollback Workflow: Archives the current branch state, creates a dedicated archive branch, and resets the working branch to a selected commit.
  • Decision History Tracking: Maintains ARCHIVE.md records that connect rollback actions with their causes, source commits, and recovery branches.
  • Use Case: When a development experiment fails, use this Skill to preserve the failed attempt and return the project to a known stable commit without losing investigation history.

Quick Start

Ask the git-snapshot-rollback skill to archive the current failed changes and roll the repository back to the specified commit while preserving a recovery branch.

Frequently Asked Questions about git-snapshot-rollback

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I rollback a Git branch without losing my failed experimental commits?

To rollback a Git branch safely, you create a dedicated archive branch capturing the current failed state before resetting the working branch to a target commit. This preserves your experimental history while restoring project stability.

What is the safest Git rollback workflow for failed development attempts?

A safe Git rollback workflow archives the current branch state, creates a recovery branch, and updates history records. It connects the rollback action with its cause, ensuring the failed implementation remains accessible for future investigation.

How do I track the reasoning behind Git repository history rollbacks?

You track Git repository rollbacks by maintaining ARCHIVE.md records that connect rollback actions with their causes, source commits, and recovery branches. This creates a traceable decision history for all controlled recovery operations.

Can I restore a Git project to a known stable commit while keeping the investigation history?

Yes, you can restore the project by archiving the current failed changes into a snapshot branch and resetting the working branch to a stable commit. The archive branch retains the investigation history for later reference.

When should I use a snapshot branch instead of a standard Git reset?

Use a snapshot branch when an experimental branch fails but contains valuable investigation work. It archives the state before a standard Git reset, preventing destructive history rewrites from permanently losing your development attempts.