sync-template

Synchronize the .claude directory from an upstream template repository.

70|42|Updated Mar 27, 2026
One-click install
npx skills add https://github.com/tranhieutt/software_development_department --skill sync-template-tranhieutt
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sync-template
Source: https://github.com/tranhieutt/software_development_department/tree/main/.claude/skills/sync-template
Command: npx skills add https://github.com/tranhieutt/software_development_department --skill sync-template-tranhieutt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Keeps the local .claude directory aligned with the official template so project updates, agents, skills, hooks, and rules are not drifted or forgotten while preserving bespoke customizations.

Core Features & Use Cases

  • Template Synchronization: Clones the upstream repo, sparse-checkout of .claude, summarizes new, modified, and local-only files, and highlights overridden local changes.
  • Safe Application: Requires user confirmation before copying template files and explicitly avoids deleting any local-only resources while honoring project-wide constraints.
  • Use Case: When onboarding a new framework or ensuring latest departmental workflows, run this skill to merge template changes into your existing Claude Code setup with clarity and confidence.

Quick Start

Run sync-template with the upstream repository URL to refresh the .claude directory while keeping your custom files intact.

Frequently Asked Questions about sync-template

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

FAQPage Schema
How do I sync my .claude directory with an upstream template repository?

To sync your .claude directory, clone the upstream repository using sparse checkout, generate a diff report of new and modified files, and confirm the copy operation to merge template changes while preserving local extras.

Will updating my Claude Code template delete my custom local files?

Updating your Claude Code template will not delete local-only resources; the synchronization process explicitly avoids removing bespoke customizations while copying template files, ensuring your custom agents and skills remain intact.

What is the best way to track configuration drift in a Claude Code project?

Tracking configuration drift involves summarizing new, modified, and local-only files between your .claude directory and the upstream template, highlighting overridden local changes before applying any updates.

Can I preview changes before applying a template-sync to my Claude agents?

Yes, you can preview changes before applying them; the process requires user confirmation after generating a diff report, allowing you to review template updates before any file copying occurs.

How does sparse checkout work when synchronizing git workflow templates?

Sparse checkout isolates the .claude directory from the upstream repository during synchronization, ensuring only the relevant template configuration files are fetched and compared against your local project setup.