What problem does it solve? Projects instantiated from a starter template drift out of date as the template evolves, and manually tracking which hooks, scripts, workflows, and skills changed is error-prone. This Skill computes the tooling diff between the project's origin commit and the current template, then proposes safe updates without touching filled-in documentation or production code. ## Core Features & Use Cases - Tooling Diff Calculation: Clones the origin template and computes a diff limited to tooling paths (.claude/, .github/scripts/, .github/workflows/, specs/_template/) since the instantiation commit recorded in .template-origin. - Safe Document Handling: Distinguishes new template documents (safe to bring in) from existing filled documents (never overwritten), and detects renamed or merged documents that would otherwise be silently duplicated. - Stricter-Check Migration: Detects checks that became stricter (e.g., check-placeholders.sh, check-inheritance.sh) and proposes resolving their findings in a separate prior commit before adopting them. - Use Case: A weekly CI workflow flags that the template published improvements; run this Skill to review the three tooling changes, apply them on a chore/update-template branch, run the test suite, and update .template-origin. ## Quick Start Ask the assistant to update the project with the latest improvements from the origin template and propose which tooling changes to apply.