rollback

A controlled way to undo committed or shipped changes in a Git project, while keeping uncommitted user work safe.

In plain words
What is it for?
Reverting the latest or a specific commit, undoing a merged pull request, restoring selected files, reversing a branch, or previewing the changes first.
Why use it?
It reduces the risk of losing work or changing the wrong files when backing out a change.

Skill for Claude CodeCodex

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add skills/harshanandak/forge/rollback
Any agent
npx skills add harshanandak/forge --skill rollback
Clone the repo
git clone --depth 1 https://github.com/harshanandak/forge

Made for: Claude Code, Codex.

Per session 60 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 823 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00060 $0.00823
Opus 5 $0.00030 $0.00411
Sonnet 5 $0.00012 $0.00165
Haiku 4.5 $0.00006 $0.00082

Measured 3d ago against content hash f2c8abdc6107, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

rollback scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 3d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.agents/skills/rollback/SKILL.md · 105 lines

How it starts

The opening of the file, as written. The whole thing — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Comprehensive rollback system with multiple methods and automatic USER content preservation.

Rollback

This skill provides safe rollback operations with comprehensive validation and USER section preservation.

Usage

bunx forge rollback

Interactive menu with 6 options:

  1. Rollback last commit - Quick undo of most recent change
  2. Rollback specific commit - Target any commit by hash
  3. Rollback merged PR - Revert an entire PR merge
  4. Rollback specific files - Restore only certain files
  5. Rollback entire branch - Revert multiple commits
  6. Preview rollback - Dry run mode (shows changes without executing)

How It Works

Safety Features

1. Working Directory Check

  • Requires clean working directory (no uncommitted changes)
  • Prevents accidental data loss
  • Prompts to commit or stash changes first

2. Input Validation

  • Commit hashes: Must match /^[0-9a-f]{4,40}$/i or be 'HEAD'
  • File paths: Validated to be within project (prevents path traversal)
  • Methods: Whitelisted to 'commit', 'pr', 'partial', 'branch'
  • Shell metacharacters: Rejected (;, |, &, $, `, (, ), <, >, \n, \r)

3. USER Section Preservation

  • Automatically extracts USER sections before rollback
  • Restores USER sections after rollback
  • Preserves custom commands in .claude/commands/custom/
  • Amends rollback commit to include restored content

4. Dry Run Mode

  • Preview affected files without executing
  • Shows what would change
  • No git operations performed

5. Non-Destructive

  • Uses git revert (creates new commit)
  • Never uses git reset --hard (destructive)
  • Preserves full git history
  • Can be undone with another rollback

USER Section Preservation

What Gets Preserved:

<!-- USER:START -->
Your custom content here
<!-- USER:END -->

<!-- USER:START:custom-name -->
Named USER section
<!-- USER:END:custom-name -->

Process:

  1. Extract all USER sections from AGENTS.md, CLAUDE.md, etc.
  2. Backup custom commands from .claude/commands/custom/
  3. Execute rollback operation
  4. Restore USER sections to current file content
  5. Restore custom command files
  6. Amend rollback commit to include restored content

Read the full file on GitHub · 105 lines

Files

What ships with it

4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 3d ago First seen · 105 lines · 60 tokens per session scan A f2c8abdc6107

Subscribe to this mod's changes

rollback is a skill published in the GitHub repository harshanandak/forge (4 stars, last pushed 3d ago), licensed MIT. It adds 60 tokens to every session and 823 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

obra/superpowers · 37 tokens

auto-perf-optimize

Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

microsoft/vscode · 62 tokens

chat-perf

Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.

microsoft/vscode · 51 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens