Ejecuta cualquier Skill en Manus
con un clic

Ejecuta cualquier Skill en Manus con un clic

update-template

Estrellas0

Forks0

Actualizado10 de julio de 2026 a las 04:06

Brings into this project the improvements its origin template received after instantiation — reads .template-origin, computes the tooling diff (skills, hooks, scripts, workflows) against the current template and offers to apply it. Use this when someone wants to update/sync the project with the template (e.g. "update the template", "pull in the template's new improvements").

Instalación

Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.

Ejecutar en Manus

Fuente

brayandiazc

brayandiazc/project-starter-template-en-ai

Abrir repositorio de GitHub Ver repositorios del creador

Descarga

Ejecutar en Manus

Ocupaciones relacionadasSOC

Basado en la clasificación ocupacional SOC

Desarrolladores de softwareOcupaciones informáticas y matemáticas·SOC 15-1252

SKILL.md

readonly

name	update-template
description	Brings into this project the improvements its origin template received after instantiation — reads .template-origin, computes the tooling diff (skills, hooks, scripts, workflows) against the current template and offers to apply it. Use this when someone wants to update/sync the project with the template (e.g. "update the template", "pull in the template's new improvements").

Sync this project's tooling with the current version of its origin template. It only touches the reusable layer — never the already-filled documentation or the code.

Step 1 — Read the origin

Read .template-origin at the root (/instantiate writes it):

repo=https://github.com/brayandiazc/project-starter-template-en-ai
commit=<template-sha-at-instantiation>
date=YYYY-MM-DD

If it doesn't exist, ask which template/variant the project came from and roughly when, and use the tag/commit from that time as the base.

Step 2 — Compute the tooling diff

Clone the template to a temporary directory and compute what changed since the origin commit, limited to the tooling paths:

git clone --quiet <repo> /tmp/tpl-update && cd /tmp/tpl-update
git diff --stat <origin-commit>..HEAD -- \
  .claude/ .github/scripts/ .github/workflows/ specs/_template/ \
  docs/conventions/_template.md

Always exclude: README.md, filled-in docs/, CHANGELOG.md, LICENSE, and any file the project has adapted (compare before overwriting; if the local file differs from the template's old version, it's a local adaptation — show it and ask).

Step 3 — Propose and apply

Present a per-file summary (new / updated / deleted in the template) and let the person choose what to apply. Work on a chore/update-template branch. Apply what's accepted, run the suite bash .github/scripts/tests/run-tests.sh if it exists, and update .template-origin with the new commit and today's date.

Step 4 — Wrap-up

Show the final diff and remind them to open a PR. Do NOT commit or push without confirmation.

Example: /update-template → "the template has 3 tooling improvements since your instantiation (new hook, links script, quality workflow); apply all 3?"

Do NOT overwrite local adaptations without asking, do NOT touch already-filled documentation or production code, and do NOT apply template changes the project chose to remove (e.g. conventions deleted on purpose).

Más de este repositorio

mismo repositorio

instantiate

brayandiazc/project-starter-template-en-ai

Instantiates this template into a real project through a guided interview — detects whether the project is new or existing, fills in the placeholders, adapts the docs to the project type, and decides the permissions policy. Use this when someone clones/adopts this template and wants to configure it for their project (e.g. "instantiate this template", "set up this template for my project", "bootstrap the project from this base").

2026-07-100

new-spec

brayandiazc/project-starter-template-en-ai

Scaffolds a new lightweight change spec by copying the spec template directory into a named spec folder. Use this when the user wants to start a spec, plan a change/feature, or create a design doc before implementing (e.g. "spec out the checkout redesign", "create a spec for the new auth flow").

2026-07-100

port-change

brayandiazc/project-starter-template-en-ai

Ports the current branch's change to this template's sibling variants (es/en × with-AI/no-AI) — translates the content, adapts or removes the AI layer depending on the target, and leaves each variant with a PR-ready branch. Use this when a template change must be replicated in the other variants (e.g. "port this change to the Spanish template", "replicate this in the variants").

2026-07-100

release

brayandiazc/project-starter-template-en-ai

Cuts a new version — moves the CHANGELOG's Unreleased section to a dated SemVer version, creates the commit and the tag, and optionally the GitHub release. Use this when someone asks to publish/cut a version or prepare a release (e.g. "cut version 1.2.0", "prepare the release", "publish a new version"). Does not push without confirmation.

2026-07-100

open-issue

brayandiazc/project-starter-template-en-ai

Drafts and creates a GitHub issue by filling out the right template from .github/ISSUE_TEMPLATE/ based on the type (bug, feature, documentation, task, or question). Use this when the user asks to open/create an issue, report a bug, or record a task/request (e.g. "open an issue for this bug", "create an issue for the new feature", "log this task"). Does not close or comment on existing issues.

2026-07-100

migration-guard

brayandiazc/project-starter-template-en-ai

Reviews a database migration before it ships to make sure it is safe — reversible, non-destructive, and backward-compatible — following the project's database conventions. Use this whenever you create, review, or approve a schema or data migration (e.g. "check this migration", "is this migration safe to deploy?").

2026-06-300

name	update-template
description	Brings into this project the improvements its origin template received after instantiation — reads .template-origin, computes the tooling diff (skills, hooks, scripts, workflows) against the current template and offers to apply it. Use this when someone wants to update/sync the project with the template (e.g. "update the template", "pull in the template's new improvements").

Sync this project's tooling with the current version of its origin template. It only touches the reusable layer — never the already-filled documentation or the code.

Step 1 — Read the origin

Read .template-origin at the root (/instantiate writes it):

repo=https://github.com/brayandiazc/project-starter-template-en-ai
commit=<template-sha-at-instantiation>
date=YYYY-MM-DD

If it doesn't exist, ask which template/variant the project came from and roughly when, and use the tag/commit from that time as the base.

Step 2 — Compute the tooling diff

Clone the template to a temporary directory and compute what changed since the origin commit, limited to the tooling paths:

git clone --quiet <repo> /tmp/tpl-update && cd /tmp/tpl-update
git diff --stat <origin-commit>..HEAD -- \
  .claude/ .github/scripts/ .github/workflows/ specs/_template/ \
  docs/conventions/_template.md

Step 3 — Propose and apply

Step 4 — Wrap-up

Show the final diff and remind them to open a PR. Do NOT commit or push without confirmation.

Example: /update-template → "the template has 3 tooling improvements since your instantiation (new hook, links script, quality workflow); apply all 3?"