rollback-guard

Propose rollback options after refactoring test failures with user confirmation.

Updated Feb 11, 2026
One-click install
npx skills add https://github.com/amijadoamijado/sd003 --skill rollback-guard
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rollback-guard
Source: https://github.com/amijadoamijado/sd003/tree/main/.gemini/skills/rollback-guard
Command: npx skills add https://github.com/amijadoamijado/sd003 --skill rollback-guard

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Detect refactoring failures and propose rollback options to the user. This skill does NOT auto-execute rollbacks - it requires user confirmation for safety.

Core Features & Use Cases

  • Context-aware checkpoint management and safe decision logging.
  • Proposal-based user interaction via AskUserQuestion to select rollback points.
  • Integration with session write and escalation paths when needed.

Quick Start

Initiate a rollback proposal flow after detecting a refactoring failure and await user decision before applying any change.

Frequently Asked Questions about rollback-guard

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

FAQPage Schema
How do I propose a rollback after test failures during refactoring?

To propose a rollback after refactoring test failures, the skill detects identical error patterns and presents structured rollback options for user confirmation. It preserves session state using /sessionwrite and requires explicit approval before applying any changes.

What is a safe rollback decision flow in session management?

A safe rollback decision flow in session management is a non-autonomous process that preserves session state with /sessionwrite and requires explicit user confirmation before applying any rollback changes. It provides a structured proposal flow to select appropriate checkpoint rollback points.

Can I automatically execute rollbacks when a refactor fails?

No, you cannot automatically execute rollbacks when a refactor fails because this tool requires explicit user confirmation for safety. It operates as a structured, non-autonomous decision flow, only proposing rollback options and awaiting your decision before applying any changes.

When do I need a checkpoint rollback proposal for refactoring?

You need a checkpoint rollback proposal for refactoring when post-batch test failures occur, identical error patterns emerge, or you explicitly request rollback evaluation. It helps safely manage refactoring failures by preserving session state and logging structured decisions.

How do I preserve session state before evaluating a rollback?

To preserve session state before evaluating a rollback, the skill uses the /sessionwrite command to save your current context. This ensures your working environment is safely checkpointed and can be restored while you review the structured rollback options.