sync

Propagate upstream template updates into downstream projects while preserving overrides.

2|1|Updated Jan 27, 2026
One-click install
npx skills add https://github.com/lucidlabs-hq/agent-kit --skill sync-lucidlabs-hq
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sync
Source: https://github.com/lucidlabs-hq/agent-kit/tree/main/.claude/skills/sync
Command: npx skills add https://github.com/lucidlabs-hq/agent-kit --skill sync-lucidlabs-hq

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Propagate upstream template updates into the downstream project to maintain parity with the latest patterns and practices.

Core Features & Use Cases

  • Sync shared skills, references, and tooling from the upstream template while preserving project-specific overrides.
  • Bootstrap a local sync workflow using scripts/sync-upstream.sh and promote.sh, enabling predictable downstream updates.
  • Use --dry-run to preview changes before applying them.

Quick Start

Run the dry-run to preview changes, then run the full sync to pull updates from the upstream template.

Frequently Asked Questions about sync

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

FAQPage Schema
How do I sync upstream template updates into my downstream project?

To sync upstream template updates, run the local bootstrap script (scripts/sync-upstream.sh) to propagate shared skills, references, and tooling while preserving project-specific overrides in your downstream project.

Can I preview upstream template changes before applying them to my project?

Yes, you can preview upstream template changes by running the sync process with the --dry-run option, allowing you to review all downstream updates before committing them to your project.

How does upstream sync handle project-specific overrides during version control updates?

Upstream sync handles project-specific overrides by preserving them during propagation, ensuring your local customizations remain intact while shared skills, references, and tooling receive the latest template updates.

Do I need a local bootstrap script to automate downstream template updates?

Yes, you need a local bootstrap script (scripts/sync-upstream.sh) to automate predictable downstream updates, track sync status in .upstream-sync.json, and use options like --all for comprehensive template propagation.

What's the best way to sync all shared skills and tooling from an upstream template?

The best way to sync all shared skills and tooling is by using the --all option with your sync-upstream.sh script, ensuring comprehensive propagation of upstream updates into your downstream project.