repo-sync-guard

To audit your repository state before committing, check for dirty, staged, and untracked files, stashes, diverged branches, and stale worktrees to prevent regressions and ensure a clean merge state.

Pre-commit code hygiene is the process of auditing a repository for unpushed changes, stashes, and branch divergences before merging. It matters because unresolved repository states cause code regressions and data loss.

Yes, you can check for Supabase migration drift without external dependencies. The audit operates entirely on the local repository state to confirm database migrations are applied correctly before pushing.

The best way to detect stale worktrees and open PRs before pushing is to run a pre-commit audit that analyzes your local repository state and identifies unmerged issues that could cause regressions.

Yes, a local repository audit catches untracked files and diverged branches. It checks the working directory state to ensure no dirty files or stashed changes will cause issues during a merge.

A limitation of a local pre-commit repository audit is that it operates solely on the local repository state and requires no external dependencies, meaning it cannot validate remote server-side CI pipeline configurations.