Skip to content
Development
Skill

/teach-change

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\".

From plugin
turbo
42074 skills

Claude Code

$ npx -y skills add tobihagemann/turbo --skill teach-change --agent claude-code

SKILL.md

teach-change.SKILL.md
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\"."

Teach Change

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.

Step 1: Identify the Change

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.

Step 2: Build the Understanding Checklist

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:

  • Lowercase
  • Replace non-alphanumeric characters with hyphens
  • Collapse consecutive hyphens
  • Trim leading and trailing hyphens
  • Truncate to 40 characters at a word boundary

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:

  • **Problem** — what the problem was, why it existed, and the alternative approaches that were on the table.
  • **Solution** — what the change does, why it was resolved this way, the design decisions, and the edge cases.
  • **Context** — why this matters and what the change impacts elsewhere.

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.

Step 3: Teach Each Item Incrementally

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.

Step 4: Confirm Full Mastery

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.

Read more
@tobihagemann
Ships withturbo

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.

Stars on GitHub

Momentum

stars in total
420
Star history of tobihagemann/turbo on GitHub, a chart by star-history.com

Other skills on turbo.

apply-turbo-handoffs

apply-turbo-handoffs

Audit the turbo lessons /self-improve wrote to .turbo/handoff/ and apply approved ones. Use when the user asks to \"read…

@tobihagemann@tobihagemannInstall Skill
apply-findings

apply-findings

Apply accepted review findings as code changes, escalating ambiguous ones to the user. Use when the user asks to \"apply…

@tobihagemann@tobihagemannInstall Skill
assess-technical-debt

assess-technical-debt

Assess project-wide technical debt (hotspots, deprecated APIs, duplication, low-value tests) into a ranked report. Use when the…

@tobihagemann@tobihagemannInstall Skill
backlog

backlog

Capture an out-of-scope improvement or accepted simplification in .turbo/backlog.md. Use proactively mid-task, or when the user…

@tobihagemann@tobihagemannInstall Skill
code-style

code-style

Enforce existence, reuse, mirror, and symmetry principles so new code stays minimal and consistent. Use when writing, changing,…

@tobihagemann@tobihagemannInstall Skill

More skills from other plugins.

brainstorming
Auto-invoked

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or…

@obra@obraInstall Skill
ask-matt

ask-matt

Ask which skill or flow fits your situation. A router over the skills in this repo.

skills2w309k
@mattpocock@mattpocockInstall Skill
accessibility
Auto-invoked

accessibility

Design, implement, and audit accessible UI to WCAG 2.2 Level AA across Web, iOS, and Android — semantic ARIA roles and labels,…

ecc2w293k
@affaan-m@affaan-mInstall Skill
compiler-commit

compiler-commit

Use when you want to verify compiler changes and commit with the correct convention. Runs tests, lint, and format, then commits…

react6d252k
@facebook@facebookInstall Skill

Questions about teach-change.

Which coding agents can use teach-change?
teach-change installs in Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode and Windsurf with the skills CLI, using each agent's flag shown on this page. Flowy's auto-invocation, which fires a skill when your prompt matches, runs in Claude Code only.