synthesis-repo-guard

Detect unsynced git repositories and report uncommitted changes and pending pushes.

15|2|Updated Mar 17, 2026
One-click install
npx skills add https://github.com/synthesisengineering/synthesis-skills --skill synthesis-repo-guard-synthesisengineering
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: synthesis-repo-guard
Source: https://github.com/synthesisengineering/synthesis-skills/tree/main/synthesis-repo-guard
Command: npx skills add https://github.com/synthesisengineering/synthesis-skills --skill synthesis-repo-guard-synthesisengineering

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

AI-assisted coding sessions often leave uncommitted or unpushed changes stranded when a session ends, breaking cross-machine sync and collaboration. The skill provides a lightweight, zero-dependency detector that scans a workspace for git repositories and reports their sync state so you can enforce a clean end to each session.

Core Features & Use Cases

  • Detects uncommitted changes in any git repository within a workspace.
  • Detects ahead/behind status relative to origin and reports counts.
  • Works as an end-of-session hook, a scheduled cron/launchd check, or a manual CLI tool for multi-machine workflows.
  • Zero AI dependencies and zero destructive actions; only reads state and reports results.
  • Returns structured results (JSON) or human-readable summaries with exit codes for integration.

Quick Start

Run the repo_sync_check.py script against your workspace to identify and surface any unsynced repositories.

Frequently Asked Questions about synthesis-repo-guard

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

FAQPage Schema
How do I check for uncommitted changes across multiple git repositories?

To check for uncommitted changes across multiple git repositories, you can run a workspace scan that discovers repos up to a configurable depth and reports their sync state. It returns structured results highlighting uncommitted changes and pending pushes.

What is the best way to automate end-of-session git sync checks?

The best way to automate end-of-session git sync checks is using a zero-dependency detector that scans your workspace for unsynced repositories. It operates as a session-end hook, scheduled cron check, or manual CLI tool for multi-machine workflows.

How does a git repository sync state detector work?

A git repository sync state detector works by scanning a workspace to discover git repos and evaluating their ahead/behind status relative to origin. It only reads state, takes zero destructive actions, and reports uncommitted changes and pending push counts.

Can I integrate git sync monitoring into CI workflows without external dependencies?

Yes, you can integrate git sync monitoring into CI workflows without external dependencies. This skill operates with zero external dependencies beyond Python stdlib and git, returning structured JSON or exit codes specifically for integration.

What are the limitations of using a read-only git sync checker?

The limitation of a read-only git sync checker is that it only detects and reports uncommitted changes and pending pushes but cannot automatically commit or push them. It operates with zero destructive actions, meaning manual intervention is required to resolve unsynced states.