← ClaudeAtlas

sync-starterlisted

Use when the user asks to pull template improvements into a spawned repo, compare starter drift, or push a generic improvement back to the starter.
ryanportfolio/STK · ★ 1 · AI & Automation · score 58
Install: claude install-skill ryanportfolio/STK
# sync-starter — two-way sync with the claude-starter template Spawned projects freeze the template at spawn date; the template keeps improving. This skill closes the gap in both directions. Template repo: `ryanportfolio/AI-Firmware` (formerly `claude-starter`; the old URL redirects, but use the new one). ## Direction A: Pull template improvements into this project ### Step 1: Wire the remote (once) ``` git remote get-url starter || git remote add starter https://github.com/ryanportfolio/AI-Firmware.git git fetch starter ``` ### Step 2: Diff the shared surface Only these paths are sync candidates: ``` git diff --stat HEAD starter/main -- AGENTS.md .agents/CODEX-SKILL-COMPATIBILITY.md .claude/skills .claude/hooks .claude/scripts .claude/settings.json ``` **Diverged-by-design — NEVER bulk-pull these:** - `CLAUDE.md` — project-configured (FILL IN sections replaced). If the template's kernel changed, read the template version (`git show starter/main:CLAUDE.md`), and hand-merge the relevant rule into the project copy. - `.claude/reference/*` — project knowledge. Template only ships skeletons. ### Step 3: Present and pick Group the diff for the user: **new skills** / **changed skills** / **Codex boundary+compatibility** / **hooks+scripts+settings**, one line each on what changed (read the actual diff, don't guess from filenames). Ask which to take (plain chat, numbered). ### Step 4: Apply selectively ``` git checkout starter/main -- <picked-paths> ``` For `settings.jso