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".