portar-cambio

Ports branch changes across sibling template variants with translation and AI-layer adaptation.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Maintaining a family of template variants (Spanish/English, with/without AI tooling) means every change must be manually replicated, translated, and adapted across up to four repositories, which is error-prone and tedious. ## Core Features & Use Cases - Change Delimitation: Diffs the current branch against main and classifies each file as general documentation, AI layer (.claude/, AGENTS.md, CLAUDE.md, specs/), or neutral tooling. - Variant-Aware Adaptation: Strips AI-layer content when porting to no-AI variants and translates content, names, and placeholders when crossing languages, following the rename map in check-parity.sh. - Per-Variant Branches with Verification: Creates a same-named branch in each destination variant, applies the adapted change, and runs its verification scripts (check-links.sh, check-placeholders.sh, tests). - Use Case: After adding a new git hook on branch feat/nuevo-hook in the Spanish AI template, run the skill to produce translated, AI-layer-adjusted feat/nuevo-hook branches in the other three variants, each ready for a PR. ## Quick Start Ask the assistant to port the current branch's changes to the other template variants, for example by saying "porta este cambio al template en inglés".

Frequently Asked Questions about portar-cambio

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

FAQPage Schema
How do I replicate a change across multiple template repository variants?▼

Create the change on a branch in one variant, then run this skill to diff against main, classify the files, and apply adapted versions to each sibling variant. Each destination gets a same-named branch with its verification scripts executed, ready for a pull request.

How are template changes translated between Spanish and English variants?▼

Translation follows the rename map in .github/scripts/check-parity.sh, covering skill names like instanciar/instantiate and placeholders like [NOMBRE_DEL_PROYECTO]/[PROJECT_NAME]. The destination variant's TEMPLATE-USAGE catalog defines the authoritative placeholder set.

Can AI-layer files be ported to template variants without AI tooling?▼

No. Files depending on the AI layer (.claude/ skills and hooks, AGENTS.md, agent mentions) are removed from the port for no-AI variants. If a native equivalent exists, such as .githooks/, the change is adapted there instead.

Does the skill push branches or open pull requests automatically?▼

No. It creates local branches in each variant and reports what was ported, adapted, or omitted, but never pushes or opens PRs without explicit confirmation. In AI-enabled variants, the /open-pr skill handles PR creation.

What happens when porting to one variant fails?▼

The failure is reported explicitly rather than leaving the variant half-updated. The closing summary lists per variant the branch created, files ported, and what was adapted or omitted and why.