contribute-turbo

# Contribute Turbo Propose an improvement to a turbo skill as an issue on `tobihagemann/turbo`. ## Step 1: Identify the Proposed Change Confirm the local repo exists: ```bash test -d ~/.turbo/repo ``` If it does not, tell the user to run the Turbo setup first and stop. Detect skills whose installed copy has drifted from the repo baseline: ```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, read both versions of every file that differs and the single version of every file present on one side only. Classify each hunk and each one-sided file: - **Correction** — a session edit meant to improve the skill upstream. Include it in the proposal. - **Customization** — a persistent local addition that belongs to this machine only (extra workflow steps, personal paths, machine-specific notes, internal references). Leave it out of the proposal. - **Upstream-newer** — content the repo copy carries and the installed copy lacks, left behind by a Skip or Exclude during an earlier update. Leave it out of the proposal. - **Ambiguous** — use `AskUserQuestion` to confirm classification. When no corrections survive classification, take the proposed change from conversation context instead. When the conversation describes no change either, tell the user there is nothing to contribute...