Verify destructive git operations before reset, rebase, or force-push execution.
npx skills add https://github.com/edobry/minsky --skill git-safety-edobry
Please help me install this Agent Skill. Skill: git-safety Source: https://github.com/edobry/minsky/tree/main/.claude/skills/git-safety Command: npx skills add https://github.com/edobry/minsky --skill git-safety-edobry
Safety protocols to prevent destructive git operations from causing data loss or remote history rewrites.
Describe the destructive operation you plan to perform and have the assistant verify the steps before execution.
High-intent search queries and answers about installing and using this skill.
To prevent data loss during git force push or rebase, use safety gates that enforce mandatory pre-checks before history rewrites. This verifies destructive operations and provides error recovery guidance to avoid overwriting remote history.
The best way to safeguard a local git repository before a destructive reset is to apply surgical operation protocols. These protocols require explicit approval workflows and pre-command verification before executing history-altering actions.
Yes, you can add approval workflows for force-push operations in shared repositories. Force-push gating requires explicit approval before execution, ensuring collaborative workflows are protected from accidental remote history rewrites.
If a git recovery operation fails after a bad rebase, follow error recovery guidance to safely undo the damage. Surgical operation protocols minimize risk by guiding you through verified steps to restore your repository state.
ferdinandybGuides automated Git commits, merges, rebases, and worktrees for safe use.
deandumEnforce pre-push checks for commit hygiene and force-push safety.
kid-sidEnforce conventional commits, branch naming, and safe force-push rules in Git workflows.
geoffjayDiagnose and recover from Git errors using reflog, cherry-pick, and reset.
