sync-template

Synchronize template repository files to child projects using a manifest.

Updated Feb 8, 2026

Search Tags:#template #configuration #monorepo #infrastructure #sync #child project

Ready to run

npx skills add https://github.com/raulnq/node-hono-react-monorepo --skill sync-template-raulnq

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: sync-template
Source: https://github.com/raulnq/node-hono-react-monorepo/tree/main/.claude/skills/sync-template
Command: npx skills add https://github.com/raulnq/node-hono-react-monorepo --skill sync-template-raulnq

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the process of synchronizing infrastructure and configuration files from a GitHub template repository to a child project, ensuring consistency and reducing manual update efforts.

Core Features & Use Cases

Infrastructure Synchronization: Copies essential template files (pure files) directly to the child project.
Configurable Merging: Handles files with existing customizations (wiring files) by presenting differences and allowing user-guided merges.
Skill Propagation: Syncs other Claude skills and configuration files.
Use Case: After updating the base ESLint configuration in the template, use this Skill to push those changes to all projects created from that template, maintaining code quality standards across your development ecosystem.

Quick Start

Use the sync-template skill to update the child project located at /Users/user/projects/my-new-app.

Frequently Asked Questions about sync-template

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

FAQPage Schema

How do I synchronize configuration changes from a template repository to child projects?▼

You can synchronize configuration changes by using a manifest file to propagate infrastructure updates from a template repository to child projects, ensuring consistency and reducing manual update efforts across your development ecosystem.

What is the best way to handle merging customized files when updating from a monorepo template?▼

The best way to handle customized files is through user-guided merges, where the synchronization process presents differences between the template and child project, allowing you to decide how to integrate the changes for files with existing customizations.

Can I push infrastructure file updates to multiple child projects at once?▼

Yes, you can propagate infrastructure file updates to child projects by running the synchronization process on each target project, copying essential template files directly to overwrite outdated configurations and maintain code quality standards.

Does template synchronization overwrite files that have been customized in the child project?▼

Template synchronization categorizes files into pure overwrites for standard infrastructure and user-guided merges for customized files, ensuring that your project-specific configurations are reviewed rather than blindly overwritten during the update process.

How does skill propagation work when syncing a template repository?▼

Skill propagation works by synchronizing other Claude skills and configuration files from the template repository to the child project, ensuring that all derived projects maintain consistent automation capabilities and development standards.

When do I need to use a manifest file for template synchronization?▼

You need to use a manifest file for template synchronization when you want to manage the propagation of infrastructure and configuration files from a template repository, specifying which files should be pure overwrites and which require user-guided merges.