apply-turbo-handoffs
Audit the turbo lessons /self-improve wrote to .turbo/handoff/ and apply approved ones. Use when the user asks to \"read…
Propose a turbo skill improvement as a GitHub issue on the turbo repo. Use when the user asks to \"contribute to turbo\", \"contribute back\", or \"upstream my changes\".
Claude Code
$ npx -y skills add tobihagemann/turbo --skill contribute --agent claude-code
Codex
$ npx skills add tobihagemann/turbo --skill contribute -a codex -y
Cursor
$ npx skills add tobihagemann/turbo --skill contribute -a cursor -y
Gemini CLI
$ npx skills add tobihagemann/turbo --skill contribute -a gemini-cli -y
GitHub Copilot
$ npx skills add tobihagemann/turbo --skill contribute -a github-copilot -y
OpenCode
$ npx skills add tobihagemann/turbo --skill contribute -a opencode -y
Windsurf
$ npx skills add tobihagemann/turbo --skill contribute -a windsurf -y
name: contribute description: "Propose a turbo skill improvement as a GitHub issue on the turbo repo. Use when the user asks to \"contribute to turbo\", \"contribute back\", or \"upstream my changes\"."
Propose an improvement to a turbo skill as an issue on `tobihagemann/turbo`.
Take the proposed changes from the lessons passed in: each names the turbo skill it targets, the change, and the session evidence behind it. Without them, take the proposed changes from conversation context. When neither describes a change to a turbo skill, tell the user there is nothing to contribute and stop.
Read each target skill's current text upstream, so each change is stated against the file as it stands on `main`:
gh api repos/tobihagemann/turbo/contents/claude/skills/<name>/SKILL.md -H 'Accept: application/vnd.github.raw'
Leave out a change whose target skill does not exist upstream, and tell the user.
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 propose.
For each change, construct a "why" explanation. The goal: the turbo maintainer should understand what happened and why the existing instructions were insufficient, without learning anything about the contributor's project.
Use this template:
> During [general workflow description], the skill's instructions [what was missing or wrong]. This caused [what happened]. The change [what it does] so that [benefit].
**Example:**
> During a code review session, the evaluate-findings skill encountered a finding with `security-default` severity. The existing instructions only handled `critical`, `high`, `medium`, and `low` severities, causing the finding to be silently dropped. The change adds `security-default` to the severity handling table so these findings are properly triaged.
The maintainer implements the change, so state it concretely alongside the "why": the file path under `claude/skills/<name>/`, the step or section it belongs in, and the exact replacement text or a diff.
Before finalizing, verify the whole proposal — the "why" explanation, the cited paths, and the proposed replacement text — contains none of the following:
Output the drafted proposal as text. Then use `AskUserQuestion` for approval. The user must approve the proposal before proceeding.
Use `TaskCreate` to create a task for each approved concern. Process concerns in order, one concern per issue.
For each concern, run the `/create-issue` skill, filing against `tobihagemann/turbo` rather than the current project's repo. The approved text from Step 2 is the issue body; leave it as approved rather than re-deriving it from conversation context.
Report each issue URL.
Then use the TaskList tool and proceed to any remaining task.
A human-gated agentic software factory for Claude Code and Codex: you decide what to build and judge the result; skills shape, build, polish, ship, and learn.
Audit the turbo lessons /self-improve wrote to .turbo/handoff/ and apply approved ones. Use when the user asks to \"read…
Apply accepted review findings as code changes, escalating ambiguous ones to the user. Use when the user asks to \"apply…
Assess project-wide technical debt (hotspots, deprecated APIs, duplication, low-value tests) into a ranked report. Use when the…
Capture an out-of-scope improvement or accepted simplification in .turbo/backlog.md. Use proactively mid-task, or when the user…
Shared changelog conventions and formatting rules. Not typically invoked directly.
Enforce existence, reuse, mirror, and symmetry principles so new code stays minimal and consistent. Use when writing, changing,…
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or…
Ask which skill or flow fits your situation. A router over the skills in this repo.