contribute-turbo

# Contribute Turbo Submit staged turbo skill improvements from `~/.turbo/repo/` back to the upstream repo. The workflow adapts based on `repoMode` in `~/.turbo/config.json`. ## Step 1: Verify Contributor Status Read `~/.turbo/config.json` and check `repoMode`: - `"fork"` or `"source"` — proceed - `"clone"` — tell the user that contributions require a fork. Offer to help convert their clone to a fork (add their fork as origin, rename current origin to upstream). Stop. - Missing config or repo — tell the user to run the Turbo setup first. Stop. Verify the repo exists and has the expected remotes: ```bash git -C ~/.turbo/repo remote -v ``` ## Step 2: Mirror Installed Skill Changes Port session corrections from `~/.claude/skills/<name>/` (where edits land first) into `~/.turbo/repo/claude/skills/<name>/` (the basis for the contribution), leaving any persistent local customizations in the installed copy untouched. Detect drifted skills: ```bash for skill in ~/.claude/skills/*/; do name=$(basename "$skill") repo_dir=~/.turbo/repo/claude/skills/"$name" [ -d "$repo_dir" ] || continue diff -rq "$skill" "$repo_dir" >/dev/null 2>&1 && continue echo "$name" done ``` For each drifted skill, first check whether the repo copy already has unstaged changes for it (`git -C ~/.turbo/repo status --porcelain claude/skills/<name>/`). If it does, use `AskUserQuestion` to ask the user how to proceed before mirroring — those changes will conflate with mirrored corrections in Step...