repo-sync-guard

Audit local repository state for pre-commit hygiene issues.

1|Updated Mar 6, 2026

Search Tags:#regression prevention #pre-commit #code hygiene #repo audit #repo state check

Ready to run

npx skills add https://github.com/DaBigHomie/ugwtf --skill repo-sync-guard

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: repo-sync-guard
Source: https://github.com/DaBigHomie/ugwtf/tree/main/.cursor/skills/repo-sync-guard
Command: npx skills add https://github.com/DaBigHomie/ugwtf --skill repo-sync-guard

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill performs a pre-commit audit to check for dirty/staged/untracked files, stashes, branches, worktrees, open PRs/Issues, and Supabase migration drift, ensuring a clean state before merging or pushing.

Core Features & Use Cases

Pre-commit Audit: Checks for potential issues that could lead to code regressions or data loss.
Branch and Worktree Analysis: Identifies diverged branches, stale worktrees, and unpushed changes.
Supabase Migration Drift: Confirms that database migrations are applied correctly.
Use Case: Before merging or pushing code, run this Skill to ensure that the repository is in a clean state and that no changes will cause a regression.

Quick Start

Run the repo-sync-guard Skill on your repository to check for pre-commit hygiene issues.

Frequently Asked Questions about repo-sync-guard

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I audit my repository state before committing to prevent regressions?▼

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.

What is pre-commit code hygiene and why does it matter for merging?▼

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.

Can I check for Supabase migration drift without external dependencies?▼

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.

What is the best way to detect stale worktrees and open PRs before pushing code?▼

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.

Does a local repository audit catch untracked files and diverged branches?▼

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.

What are the limitations of a local pre-commit repository audit?▼

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.