revert-check

To detect accidental git reverts before commit, analyze your working tree against the default branch using git log and git diff. This process evaluates recent file history and net deletions to flag suspicious reversions caused by stale buffers or bad stash pops.

Accidental reverts in a git working tree are typically caused by stale buffers, bad stash pops, and branch-switch mistakes. These rollback-prone scenarios silently undo recently merged work by overwriting files with older versions during local checks.

Yes, you can run pre-commit code review checks for both staged and unstaged files. The detection mechanism evaluates working-tree edits against the baseline by applying recency, deletion direction, and deletion magnitude heuristics to surface risky reversions.

Prevent bad stash pops from undoing merged fixes by comparing working-tree edits against the default branch before committing. This heuristic safety check flags modified files that recently changed and now appear to be rolling back.

Yes, revert detection supports both advisory warning mode and strict blocking mode. Advisory mode provides warning-only review for risky diffs, while strict mode enforces commit blocking to gate reversions during pre-push validation and QA handoffs.

Detecting git reverts using deletion magnitude heuristics relies on recency, deletion direction, and deletion magnitude against the default branch. It may not catch intentional large deletions of old code or subtle logic changes that do not register as net deletions.