sync-template

Synchronizes the .claude workflow directory from a central Git template repository.

16|1|Updated May 5, 2026
One-click install
npx skills add https://github.com/AIBiz-Automatyzacje/workspace-template-mobile --skill sync-template-aibiz-automatyzacje
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sync-template
Source: https://github.com/AIBiz-Automatyzacje/workspace-template-mobile/tree/main/.claude/skills/sync-template
Command: npx skills add https://github.com/AIBiz-Automatyzacje/workspace-template-mobile --skill sync-template-aibiz-automatyzacje

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Keeping the Claude Code workflow machinery (.claude/ skills, agents, rules, hooks, workflows, templates, settings.json) up to date across multiple projects is tedious and error-prone when done manually. This Skill pulls the latest version from the central workspace-template-mobile repository and applies changes automatically, with backups for rollback. ## Core Features & Use Cases - Automatic template sync: Clones the template repo, compares file contents, classifies changes as new/modified/removed, and applies them in one run. - Safe overwrite with backup: Template always wins for shared files, but overwritten and deleted files are first copied to a timestamped backup directory as a rollback path. - Local file protection: Project-local files the template never shipped stay untouched; only files previously delivered by the template and later withdrawn are removed (tracked via a manifest). - Use Case: After copying the template into a new Expo project, run the sync to pull the newest skills and agents; or use --dry-run to preview what changed in the template before applying. ## Quick Start Ask the assistant to synchronize the .claude configuration with the central template, optionally requesting a dry-run preview first.

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 folder with a central template repository?

Run the bundled script with bash .claude/skills/sync-template/scripts/sync-template.sh. It shallow-clones the template repo, compares file contents, and applies new, changed, and removed files automatically while backing up anything it overwrites.

How can I preview template changes before applying them?

Pass the --dry-run flag to the sync script. It prints the full report of new, modified, and deleted files with counts, but writes nothing to disk, so you can review the scope of changes first.

Will syncing overwrite my project-local skills or settings?

No. Files that exist locally but were never shipped by the template remain untouched, and settings.local.json is explicitly excluded. Only files previously delivered by the template and later removed upstream are deleted, tracked via the .template-manifest file.

What happens if the git clone of the template fails?

The script reports the clone error with the git stderr output and suggests running gh auth login or checking network access. This usually means the repository is private or credentials are missing; the script does not retry automatically.

Can I force a reset of .claude to the template version?

Yes, use the --force flag. It applies the template even when the stored SHA matches the upstream SHA, which is useful after manual edits inside .claude that you want to revert to the template state.