sync-with-template

Template synchronization pushes generic improvements like skills, instructions, and shared specs to the upstream template using git subtree. It applies across projects that adopt the template while keeping project-specific files out.

To prevent project-specific files from being pushed to a shared git template, the workflow enforces an abstraction step that removes local references before pushing. This ensures only generic assets are synchronized upstream.

You do not need special git dependencies to pull template updates into a derived project. This synchronization process requires only standard Git commands to manage subtree operations.

The standard workflow for pushing generic improvements back to a project template involves creating a branch from the template main, cherry-picking generic files, and submitting a pull request upstream before pulling updates back locally.

Pushing local references to a shared template causes synchronization errors because it breaks project isolation. The template requires an abstraction step to remove local context before pushing to ensure only generic assets are shared.

Yes, you can use git subtree to bidirectionally sync shared specs between derived projects and a central template. This method codifies bidirectional improvements ensuring alignment while preserving project context.