sync-template

Merge template repository updates into projects while preserving custom changes.

Updated Mar 28, 2025

Search Tags:#automation #version-control #conflicts #dry-run #template-sync #hash-based-merge #project-maintenance

Ready to run

npx skills add https://github.com/gileck/app-template-ai --skill sync-template

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: sync-template
Source: https://github.com/gileck/app-template-ai/tree/main/.ai/skills/template/sync-template
Command: npx skills add https://github.com/gileck/app-template-ai --skill sync-template

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams keep their projects aligned with the latest template changes while preserving custom work, reducing manual merge overhead and drift.

Core Features & Use Cases

Hash-based merging: Detects template-only changes versus project changes and applies safe updates automatically where possible.
Conflict handling: Flags conflicts and guides manual resolution to preserve project customizations.
Preview before apply: Dry-run previews show what would change without modifying files.
Selective sync: Supports skipping or ignoring specific files to avoid overwriting team-specific work.

Quick Start

Install and initialize template tracking, preview updates with dry-run, then apply updates with minimal disruption. To start syncing: run yarn init-template https://github.com/YOUR_USERNAME/app-template-ai.git followed by yarn sync-template after reviewing the preview.

Frequently Asked Questions about sync-template

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

FAQPage Schema

How do I sync a template repository with my existing project without losing custom changes?▼

Template syncing merges updates from a template repository into your existing project while preserving custom changes. It uses hash-based change detection to identify template-only updates and applies safe modifications automatically, flagging conflicts for manual resolution when necessary.

Can I preview template updates before applying them to my project?▼

Yes, dry-run previews show exactly what would change without modifying any files. You can review the proposed template updates, skip or ignore specific files, and selectively apply only the safe changes to avoid overwriting team-specific work.

How does hash-based merge detection work for project template synchronization?▼

Hash-based merging detects whether changes originate from the template or your project by comparing file hashes. This allows the system to automatically apply template-only updates while preserving your custom modifications, reducing manual merge overhead and project drift.

What do I need to set up before syncing template updates to my local project?▼

You need a local clone configured with template-tracking metadata. Initialize it by running yarn init-template with your template repository URL, then execute yarn sync-template to preview and apply updates with minimal disruption.

How do I handle conflicts when merging template updates into a customized project?▼

When conflicts arise during template synchronization, the system flags them and guides manual resolution to preserve your project customizations. Selective sync also lets you skip or ignore specific files to avoid overwriting team-specific work.

What is the best way to maintain project alignment with upstream template changes?▼

The best way to maintain alignment is using a template-sync workflow with hash-based change detection. It automatically applies safe updates from the template repository while flagging conflicts, reducing manual merge overhead and drift over time.