git-safety

Git-safety enforces safe Git operations by blocking or warning on destructive commands like force push, hard reset, and git clean. It prompts for explicit permission or suggests safer alternatives such as stash or pull --rebase to protect collaborative work from irreversible data loss.

Apply git-safety rules before pushing to enforce policy checks across your workflow. The Skill prevents force push, hard reset, and dangerous cleanup operations, requiring team confirmation for risky actions and promoting stash, rebase, and explicit permission workflows instead.

Yes. Git-safety applies during push, reset, and cleanup workflows to prevent irreversible changes when multiple developers work in quick succession. It stops destructive operations and encourages safer practices like pull before push and explicit team approval.

Force push and hard reset can overwrite teammates' work without recovery. Git-safety prevents these operations by default, reducing the risk of irreversible data loss and enforcing best practices that keep collaborative repositories stable and recoverable.

Git-safety implements policy checks that prompt for confirmation on force push, hard reset, and git clean operations. It encourages using stash, pull --rebase, or explicit permission workflows, ensuring developers make intentional choices about potentially destructive actions.