upgrade-template

To upgrade a project template without overwriting custom changes, run a script that diffs changed files and copies new ones while explicitly preserving project-owned paths. This ensures template synchronization across branches or repos without losing user-owned modifications.

The best way to synchronize template updates across multiple repositories is to use an upgrade script that orchestrates safe updates. It automatically patches changed files and copies new template files, ensuring consistent evolution while preserving project-specific changes.

File diffing and patching during template upgrades works by comparing existing project files against the new template source. The script identifies discrepancies, applies template improvements to changed files, and copies entirely new files, all while leaving project-owned paths untouched.

Yes, you can apply CLAUDE.MD template updates to multiple branches by running the upgrade-template script across each target. It safely synchronizes template improvements by diffing and patching changed files while preserving your custom modifications in every branch.

The template upgrade script preserves certain project files to prevent overwriting user-owned customizations. It recognizes project-owned paths and skips them during the synchronization process, only diffing and patching shared files to ensure seamless template evolution.

Yes, you need access to the template source to run a codebase upgrade. The upgrade-template script requires the source files to identify new additions and generate diffs for patching existing files, ensuring your project receives the correct template improvements.