gitrules

Prevent data loss from destructive git commands by enforcing a safety-first workflow that mandates repository state inspections using git status and git diff before execution. This protocol requires explicit user confirmation and provides guardrails to manually undo or stash changes.

The best way to review changes before risky git reset or revert operations is to implement a structured safety protocol that blocks execution until you inspect the planned changes. This guided approach prompts you to stash work or confirm actions before proceeding.

This git safety workflow requires no external dependencies or specific components to function. It operates as a standalone protocol that applies across any repository to enforce mandatory checks and guardrails during feature development, debugging, or collaboration.

You can use git stash to protect uncommitted work during destructive version-control operations by following a safety protocol that prompts you to stash changes. This guardrail ensures your work is safely set aside until you explicitly confirm the destructive action.

You should avoid running git checkout on a file without reviewing the diff first because it overwrites local changes and causes data loss. The safety protocol enforces mandatory diff reviews and explicit confirmation before allowing such destructive actions to proceed.