Rollback Check

Validate staged git diffs for safe rollback procedures before commits.

1|Updated Mar 7, 2026

Search Tags:#git #code review #rollback #safety #risk assessment #pre-commit

Ready to run

npx skills add https://github.com/jimmymalhan/codereview-pilot --skill rollback-check

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: Rollback Check
Source: https://github.com/jimmymalhan/codereview-pilot/tree/main/.claude/skills/rollback-check
Command: npx skills add https://github.com/jimmymalhan/codereview-pilot --skill rollback-check

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents risky changes by ensuring a safe and documented rollback path exists before code is committed or deployed.

Core Features & Use Cases

Pre-commit Verification: Automatically checks for a safe rollback strategy before a commit is finalized.
Risk Assessment: Identifies potential data loss or one-way operations.
Use Case: Before merging a database schema change, this Skill will verify that a down-migration script exists and has been tested, preventing accidental data loss.

Quick Start

Run the rollback check skill to verify the safety of the staged changes.

Frequently Asked Questions about Rollback Check

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

FAQPage Schema

How do I ensure a safe git rollback path exists before committing code changes?▼

To ensure a safe git rollback path before committing, you can run a rollback check that analyzes staged git diffs and branch context to block commits lacking a documented revert strategy. This prevents risky or irreversible operations.

What is a pre-commit rollback check and how does it prevent data loss?▼

A pre-commit rollback check is a verification process that identifies potential data loss by validating a safe revert path. It blocks commits or PRs for breaking changes, ensuring operations like database schema modifications have tested down-migration scripts.

How do I verify a down-migration script exists before merging a database schema change?▼

To verify a down-migration script exists before merging a database schema change, run a rollback check to analyze the staged diff and blast-radius risk. It blocks the commit if no tested and safe revert path is documented.

Can I assess blast-radius risk for breaking API changes before a git commit?▼

Yes, you can assess blast-radius risk for breaking API changes before a git commit by running a rollback check. It evaluates the staged changes and current branch context to block commits that lack a safe and reversible revert path.

When do I need a rollback verification check for my code review process?▼

You need a rollback verification check during code review when changes involve risky operations like database schema modifications or breaking API changes. It ensures a tested down-migration or safe revert path exists before the commit is finalized.

Does the rollback check require any specific git hooks or dependencies to work?▼

No specific git hooks or dependencies are required. The rollback check operates by analyzing staged git diffs, blast-radius risk assessments, and current branch context directly to validate the existence and safety of rollback procedures.