apply-turbo-handoffs
Audit the turbo lessons /self-improve wrote to .turbo/handoff/ and apply approved ones. Use when the user asks to \"read…
Teach the user a change through interactive tutoring and quizzing until mastery. Use when the user asks to \"teach me this change\", \"help me understand what changed\", or \"quiz me on this\".
Claude Code
$ npx -y skills add tobihagemann/turbo --skill teach-change --agent claude-code
Codex
$ npx skills add tobihagemann/turbo --skill teach-change -a codex -y
Cursor
$ npx skills add tobihagemann/turbo --skill teach-change -a cursor -y
Gemini CLI
$ npx skills add tobihagemann/turbo --skill teach-change -a gemini-cli -y
GitHub Copilot
$ npx skills add tobihagemann/turbo --skill teach-change -a github-copilot -y
OpenCode
$ npx skills add tobihagemann/turbo --skill teach-change -a opencode -y
Windsurf
$ npx skills add tobihagemann/turbo --skill teach-change -a windsurf -y
name: teach-change description: "Teach the user a change through interactive tutoring and quizzing until mastery. Use when the user asks to \"teach me this change\", \"help me understand what changed\", or \"quiz me on this\"."
Act as an effective teacher whose goal is the user's deep understanding of a change. Work incrementally, confirm mastery at each stage before advancing, and keep going until the user has demonstrated understanding of everything on the checklist.
Pick the subject in priority order:
1. A commit, PR, or path passed as an argument — use that 2. The work produced in the current session — use that 3. Uncommitted work from `git status` and `git diff` — use that 4. The most recent commit when nothing else is in scope
When the guess is not obvious, name what was picked so the user can redirect before teaching starts.
Read the change in full: the diff, the touched files, related code, and any commit messages, plan, or PR description that explain intent.
Pick a slug for the change under study:
If the change is anchored to an existing plan at `.turbo/plans/<slug>.md`, reuse that plan's slug verbatim. If `.turbo/understand/<slug>.md` already exists, append `-2`, `-3`, etc. until the path is free. Do not overwrite: an existing checklist belongs to a session that may still be open.
The user may pass an explicit slug or output path; honor it. A path that already exists is background input naming the change to study, not a destination — treat it as the output path only when the request says so explicitly. When an explicit output path already exists, use `AskUserQuestion` to ask whether to overwrite, append a numeric suffix, or pick a different slug.
State the chosen path before continuing.
Write a running checklist to that path, with a checkbox per item, grouped into three sections:
Cover both high level (motivation) and low level (business logic, edge cases). Update this file as the session progresses: check items off only once the user has demonstrated understanding, and add items when teaching surfaces a gap.
Work through the checklist one item at a time. Do not advance to the next item until the user has demonstrated mastery of the current one. For each item:
1. **Have the user restate first.** Ask what they already understand about the item before explaining anything. This reveals where the gaps are. 2. **Fill the gaps from there.** Correct misconceptions and supply what is missing. Drill into why, then the deeper why behind it, and cover what and how as well. 3. **Adjust depth on request.** The user may ask for a simpler explanation, more detail, or a worked walkthrough as if onboarding a new teammate. Match the level they ask for. 4. **Show the evidence.** Display the relevant code, or use the debugger, when seeing it makes the point land. 5. **Confirm mastery by quizzing.** Verify understanding before checking the item off. Pose open-ended recall questions as plain text. For multiple-choice questions, use `AskUserQuestion`: vary the position of the correct answer across questions, and reveal the correct answer only after the question is submitted. If the answer reveals a gap, return to step 2 for that item before moving on.
The session continues until every checklist item is checked off. When the user signals they want to stop early but items remain, use `AskUserQuestion` to confirm whether to end now or keep going. Once all items are demonstrated, summarize what the user now understands and close out.
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.