validate-git-safety

What problem does it solve?

History-rewriting Git operations (like filter-branch or rebase --all) can accidentally corrupt version branches or lead to irreversible data loss. This Skill acts as a critical safeguard, preventing such catastrophic mistakes and ensuring the integrity of your repository.

Core Features & Use Cases

• Version Branch Identification: Automatically detects and protects critical v[0-9]+ version branches.
• Command Impact Analysis: Analyzes Git commands for dangerous flags (--all, --branches) that could affect protected history.
• Target Branch Validation: Verifies that the target of a Git operation is not a protected version branch.
• Blocks or Warns: Explicitly blocks dangerous operations or issues warnings for potentially risky ones, providing safe alternatives.
• Use Case: Before attempting a git filter-branch operation to remove sensitive data from your repository's history, use this Skill to validate the command. It will ensure you don't accidentally rewrite the history of your v21 release branch, preventing a major incident.

Quick Start

Before running a potentially dangerous Git command: COMMAND="git filter-branch --tree-filter 'rm -f secrets.txt' HEAD" /workspace/main/.claude/scripts/validate-git-safety.sh
--command "$COMMAND"