Destructive Git Guard

The problem

AI agents with terminal access can execute destructive commands like git reset --hard or rm -rf, permanently deleting hours of uncommitted work without warning. Standard agents often prioritize efficiency over safety, leading to irreversible data loss in environments without remote backups.

What it does

• Intercepts high-risk commands including git reset, checkout, clean, push --force, and rm.
• Forces a mandatory git status check to audit the working tree before any destructive proposal.
• Calculates and reports the exact scope of potential data loss to the human operator.
• Blocks execution until explicit, per-command confirmation is received for the specific action.
• Recommends non-destructive alternatives like git stash or branch creation before proceeding with deletions.

Why this beats prompting it yourself

Simple system prompts for "safety" are often ignored during complex task execution. This skill enforces a specific pre-flight checklist and state-check workflow that makes silent data loss architecturally difficult for the agent.

Use cases

• Protecting local-only projects that lack a remote origin or recent commits.
• Managing agents running in external terminals or CLI wrappers outside of IDE undo-history.
• Preventing accidental history overwrites during complex rebase or force-push operations.
• Ensuring untracked files are not nuked during automated workspace cleanup.

Known limitations

Requires the agent to have access to standard Git and shell binaries to perform state checks. It cannot prevent data loss if the agent is explicitly instructed by the user to bypass all safety protocols.