git-guardrails-claude-code

Git guardrails enforce safety by first classifying commands like force push or reset --hard as destructive, warning about specific risks of irreversible repository damage, and promoting safer alternatives that preserve local changes.

The safest way to discard local changes involves using guardrails that protect local work by promoting preservation strategies during corrective actions, ensuring unfinished work is kept safe instead of being blindly overwritten by risky checkouts.

Git safety guardrails classify risky checkout patterns and backtracking operations by evaluating if the requested action may discard work, identifying it as destructive, and warning the user about specific risks before any history-rewriting occurs.

Yes, you can use git guardrails to check a command before running it by asking the AI to apply the guardrails to your planned command, which will then recommend the safest alternative for your specific scenario.

You should use git safety guardrails whenever you plan history-rewriting operations like hard resets, risky checkouts, or force pushes, as these commands risk irreversible repository damage and require safety-first guidance to protect your work.