sync-repos

Detect drift between private and public repos and validate parity.

97|18|Updated Feb 9, 2026

Search Tags:#automation #git #validation #sync #drift #repositories #pii-scan

Ready to run

npx skills add https://github.com/thatrebeccarae/claude-marketing --skill sync-repos

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: sync-repos
Source: https://github.com/thatrebeccarae/claude-marketing/tree/main/skills/sync-repos
Command: npx skills add https://github.com/thatrebeccarae/claude-marketing --skill sync-repos

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Keeps private development repos aligned with their public counterparts, preventing drift and accidental exposure of sensitive data.

Core Features & Use Cases

Drift detection between a dev and public repo.
Run a controlled sync to propagate changes from dev to public.
Auto-detect common exclusions and generate setup for new repo pairs.
Post-sync validation including a PII/secrets scan to ensure a safe public release.

Quick Start

Issue a drift check for your repo pair, then run a sync and verify results.

Frequently Asked Questions about sync-repos

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

FAQPage Schema

How do I detect drift between private and public git repositories?▼

Detecting drift between private and public git repositories requires calculating parity across file paths and content. This Skill identifies discrepancies between dev and public repo pairs, ensuring changes are tracked before synchronization.

What is the best way to sync a development repo with its public counterpart?▼

The best way to sync a development repo with its public counterpart is through controlled script execution that propagates changes while auto-detecting common exclusions. This ensures only intended updates move from private to public.

How can I scan a public repository for PII and secrets before release?▼

Scanning a public repository for PII and secrets involves running post-sync validation that checks file paths and content. This Skill executes PII and secrets scanning to ensure a safe public release without exposing sensitive data.

Can I automatically generate setup for new private and public repository pairs?▼

Automatically generating setup for new private and public repository pairs is supported. This Skill auto-detects common exclusions and generates the necessary configuration to keep new dev-public pairs aligned and safe from the start.

How do I validate repo parity after synchronizing changes?▼

Validating repo parity after synchronizing changes involves running post-sync checks that confirm the public repo matches the dev repo. This Skill performs path validation and drift calculation to verify alignment and safe release.

What limitations exist when automating git repository synchronization?▼

Limitations when automating git repository synchronization include the need for accurate path validation and dependency on controlled script execution. This Skill requires proper exclusion configuration to prevent unintended data exposure during the sync process.