submodule-setuplisted

# Submodule Setup <overview> Automates the setup of git submodule architecture with fully automated parent-child synchronization via GitHub Actions. Transforms branch-based content separation into always-present submodule directories, eliminating context-switching for agents and developers. **Result:** ``` parent-repo/ ├── src/ ├── docs/ <- submodule (always present) └── exports/ <- submodule (always present) ``` </overview> ## Reference material This skill is phase-driven and the phase bodies are long. Load what the current step needs rather than reading everything up front: | File | Read it when | |------|--------------| | `references/phases.md` | Running any phase — full bodies for Phases 0-10 and Finalization | | `references/protocols.md` | You need the tool-usage guide, manual-intervention handoff format, state-file schema, or default escalation rules | | `references/troubleshooting.md` | A phase fails or a submodule misbehaves | | `references/decision-rationale.md` | The user asks why submodules over alternatives | Templates live in `assets/`, helper scripts in `scripts/`. Resolve both through `${CLAUDE_PLUGIN_ROOT}` — never a hardcoded install path. ## Prerequisites ```bash "${CLAUDE_PLUGIN_ROOT}/skills/submodule-setup/scripts/validate-prerequisites.sh" ``` **Required:** - GitHub CLI (`gh`) installed and authenticated - Git 2.x+ - Repository with push access - Ability to create fine-grained PAT <workflow> ## Workflow ``` Phase 0: Backu