← ClaudeAtlas

apply-turbo-handoffslisted

Audit the turbo lessons /self-improve wrote to .turbo/handoff/ and apply approved ones. Use when the user asks to "read .turbo/handoff and let me know what you think" or "process the turbo handoffs".
tobihagemann/turbo · ★ 421 · Code & Development · score 89
Install: claude install-skill tobihagemann/turbo
# Apply Turbo Handoffs ## Task Tracking At the start, use `TaskCreate` to create a task for each step: 1. Audit the handoffs 2. Act on the user's reply 3. Apply the approved changes 4. Close out the handoffs 5. Run `/stage-commit-push` skill ## Step 1: Audit the Handoffs Read every file in `.turbo/handoff/`. Audit the handoffs that propose lessons for turbo files. Name any handoff that instead carries a session's in-flight work, and leave it untouched. When no lesson handoff exists, present "No lesson handoffs in `.turbo/handoff/`." Mark Steps 2 through 5 completed, then use the TaskList tool and proceed to any remaining task. Take each handoff's evidence as a record of the incident, and audit its remedy against the file it targets before recommending any of it: - **Gap** — confirm the gap still exists in the current text, is not already handled elsewhere in the skill, its references, or the `SKILL-CONVENTIONS.md` of the edition the target lives in (`claude/` or `codex/`), and was not already rejected by a decision recorded in auto memory or the target's git history. - **Diagnosis** — ask whether the real finding is that the skill should not have run there, or that nothing was broken, rather than that the skill must handle the case. Before concluding either, check whether the user had to step in to finish something the skill left undefined. Treat such an intervention as a gap, look for it in the design of the skill the lesson targets as well as where the handoff's reme