sync-template

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.

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.

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.

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.

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.

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.