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: Review Pending Changes Check what changes exist in the local repo: ```bash git -C ~/.turbo/repo diff --name-only git -C ~/.turbo/repo diff --cached --name-only ``` If there are unstaged changes to skill files, stage the specific skill directories that changed: ```bash git -C ~/.turbo/repo add skills/<name>/ ``` If there are no changes at all, tell the user there is nothing to contribute and stop. Present the changes in a summary table: ``` | # | Skill | Change Summary | |---|-------|----------------| | 1 | /evaluate-findings | Added handling for security-default findings | | 2 | /self-improve | Clarified routing for trusted reviewer feedback | ``` Use `AskUserQuestion` to confirm which changes to include. If the user deselects some, unstage those files. ## Step 3: Validate Skill Quality Read `~/.turbo/repo/SKILL-CON...