git-safety

Preventing data loss during destructive git operations requires enforcing pre-operation protocols, suggesting safer alternatives, and confirming user intent before executing commands like force push or reset hard. This skill provides critical safety checks and recovery commands to protect your work.

Force pushing to a shared git branch can overwrite remote commits and cause irreversible data loss for collaborators. This skill identifies such destructive operations, warns you of the specific risks, and guides you through safer alternative commands to preserve team history.

To safely perform a git reset hard without losing uncommitted changes, this skill shows exactly which commits and local modifications will be lost, offers to stash your work, and creates a backup branch before executing the destructive command.

Recovering deleted commits after a git branch -D command is possible using included recovery commands and best practices. This skill enforces pre-operation checks and confirms your intent before execution, ensuring you have backup procedures in place to retrieve lost work.

Managing git safety during rebasing on shared branches involves enforcing pre-operation protocols and suggesting safer alternatives to prevent data loss. This skill confirms user intent and provides critical safety checks before executing potentially destructive rebase commands.

Git clean requires safety checks to prevent losing untracked files because it is a destructive operation that permanently deletes data. This skill warns about the operation, confirms your intent, and guides you through pre-operation backup procedures to avoid data loss.