sync

Reconcile .claude/ directory drift against the upstream claude-kit foundation.

Updated Apr 28, 2026
One-click install
npx skills add https://github.com/ChazzCoin/claude-kit --skill sync-chazzcoin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sync
Source: https://github.com/ChazzCoin/claude-kit/tree/main/kit/skills/sync
Command: npx skills add https://github.com/ChazzCoin/claude-kit --skill sync-chazzcoin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reconcile this project's .claude/ directory against the upstream claude-kit foundation repository. Fetches the kit at HEAD, diffs every kit-managed file (skills, task-rules, and task templates), classifies drift, and proposes per-file pulls. Never auto-commits, never overwrites local overrides, and never touches project-content files.

Core Features & Use Cases

  • One-way sync from kit to project that preserves local edits unless explicitly overridden.
  • Fetches the kit HEAD, diffs kit-managed files using the kit's manifest, and surfaces per-file drift as actionable updates.
  • Supports conflict handling for overrides and overlaps and renders a guided decision prompt before applying changes.
  • Ideal for maintaining alignment when integrating updates from claude-kit without risking unintended changes to project content.

Quick Start

Run /sync to begin aligning this project with claude-kit and review the proposed updates before applying.

Frequently Asked Questions about sync

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

FAQPage Schema
How do I sync my project's .claude directory with upstream claude-kit updates?

To sync your project's .claude directory with upstream claude-kit updates, run the /sync command. It fetches the kit HEAD, diffs kit-managed files, and prompts you to review proposed per-file pulls before applying any changes.

What happens when local overrides conflict with claude-kit foundation files during a sync?

When local overrides conflict with claude-kit foundation files during a sync, the tool never auto-overwrites. It classifies the drift and renders a guided decision prompt, letting you explicitly choose how to handle each overlapping file.

Does the claude-kit sync process automatically commit changes to my repository?

The claude-kit sync process never auto-commits changes to your repository. It enforces a one-way pull model and only applies updates after you explicitly approve the proposed file diffs from the structured delta timeline report.

How do I check for drift between my project files and the claude-kit foundation?

To check for drift between your project files and the claude-kit foundation, run /sync. It compares your pinned SHA against the fetched kit HEAD, classifies file differences, and generates a structured report with actionable update options.

Do I need a foundation.json file to reconcile drift with claude-kit?

Yes, you need a foundation.json file to reconcile drift with claude-kit. The sync process requires access to this manifest to identify kit-managed files, including skills, task-rules, and task templates, before performing any diff operations.

Will syncing claude-kit updates overwrite my project content files?

Syncing claude-kit updates will not overwrite your project content files. The reconciliation process strictly targets kit-managed files like skills and task templates, leaving your project-content files untouched and preserving local edits unless explicitly overridden.