actualizar-plantilla

Synchronizes project tooling with upstream template improvements via git diff analysis.

15|22|Updated May 5, 2024
One-click install
npx skills add https://github.com/brayandiazc/project-starter-template-es-ai --skill actualizar-plantilla-brayandiazc
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: actualizar-plantilla
Source: https://github.com/brayandiazc/project-starter-template-es-ai/tree/main/.claude/skills/actualizar-plantilla
Command: npx skills add https://github.com/brayandiazc/project-starter-template-es-ai --skill actualizar-plantilla-brayandiazc

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about actualizar-plantilla

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

FAQPage Schema
How do I update a project instantiated from a GitHub template?▼

Read the .template-origin file to find the origin repo and instantiation commit, clone the template, and run git diff between that commit and HEAD limited to tooling paths. Then propose the changes per file and apply accepted ones on a chore/update-template branch.

How to sync template changes without overwriting my documentation?▼

Limit the diff to tooling directories like .claude/, .github/scripts/, and .github/workflows/, excluding README, CHANGELOG, and filled docs. Documents that do not exist locally are safe to bring in; existing ones are only listed for manual review.

What happens if the template renamed or merged a document?▼

Renamed documents are not replaced but duplicated, leaving both versions silently. Check the template's CHANGELOG for Changed and Removed entries mentioning file paths, then migrate content pair by pair and delete the old file.

Why does CI fail after adopting an updated template check?▼

A check that became stricter flags many pre-existing issues at once, turning the first PR red. Run the new check before adopting it, resolve its findings in a separate prior commit, then introduce the check itself.

What if the .template-origin file is missing?▼

Ask which template and variant the project came from and the approximate instantiation date, then use the template tag or commit from that period as the diff base instead of the recorded commit.