メニュー
Use when the user wants a code-change walkthrough, diff review, or PR explanation. Covers reviewer-style summary, old vs new behavior, why each hunk exists, and concise engineer knowledge transfer.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
Use when the user wants a strict approval packet for a code change: recommendation, scope, evidence, residual risk, rollback impact, and required follow-ups in a compact reviewer-facing format.
Enforces presentation-first React components by moving non-trivial hook logic into domain-named custom hooks. Use when implementing tickets or feature requests that touch React or TSX components, especially when creating or editing UI components with multiple hooks, derived state, effects, or async data hooks such as useQuery, useMutation, Convex queries, or similar.
Specialized intelligence for 'seeing' hidden portability issues and navigating the Skill Harbor Lighthouse Workspace.
Reviews uncommitted changes and branch-vs-base diffs like a strict automated reviewer, focusing on the kinds of issues Cursor Bot, Greptile, CodeRabbit, or Qodo are likely to flag before CI/CD. Use when the user asks for early review, pre-CI feedback, uncommitted-change review, or wants to catch issues before the pipeline does.
SOC 職業分類に基づく
| name | teachback |
| description | Use when the user wants a code-change walkthrough, diff review, or PR explanation. Covers reviewer-style summary, old vs new behavior, why each hunk exists, and concise engineer knowledge transfer. |
| targets | ["*"] |
| tags | ["review","diff","teachback","knowledge-transfer"] |
| contracts | {"requires":{"change_target":"string"},"produces":{"review_output":"markdown","residual_risks":"markdown","key_takeaways":"markdown"}} |
| argument-hint | [--scope|--s staged|working|commit:<sha>|range:<base>..<head>|files:<paths...>] [--mode|--m review|teachback|combined] [--audience|--a engineer|approver|manager|onboarding] [--evidence|--e minimal|standard|strict] [--risk|--r brief|full|only] [--flow] [--idea-shifts on|off] [--line-refs|--lr on|off] [--brief|--deep] <review request> |
Explain a concrete change set so someone can both review it and learn from it.
Default behavior:
--mode combined--audience engineer--scope staged, then working if staged is empty--evidence standard--risk brief--idea-shifts on--line-refs on when references are availableUse this when the user asks for:
Do not use this when:
If the user wants a strict approval packet, structured review artifact, or lead/reviewer gating output, escalate to approver-packet.
--scope / --sstagedworkingcommit:<sha>range:<base>..<head>files:<paths...>--mode / --mreview — reviewer-style diff review onlyteachback — learning-oriented walkthrough onlycombined — review first, then teachback--audience / --aengineerapprovermanageronboarding--evidence / --eminimalstandardstrict--risk / --rbrieffullonly--flowAdd end-to-end runtime or state flow when the change touches behavior across layers.
--idea-shiftson — explain conceptual or mental-model changes alongside code changesoff — focus on code and behavior only--line-refs / --lronoffFor each meaningful hunk, cover:
When --idea-shifts on and a meaningful conceptual change exists, also cover:
When relevant, include:
--mode, --audience, and --risk--evidence--line-refs onPrefer this order unless the user asks for something else:
## Idea shifts## Concepts / principlesMode adjustments:
review: omit teachback sectionteachback: keep summary, teachback, evidence, takeawaysrisk only: output only risks, rollback, follow-upsMake this distinction explicit for the user:
Preferred subsection labels:
## Idea shifts## Concepts / principlesIf no concrete change target is provided:
change_target: string — staged diff, working diff, commit, range, PR diff, or file listreview_output: markdown — review, teachback, or combined explanationresidual_risks: markdown — risk and follow-up noteskey_takeaways: markdown — concise engineering lessonsFor reusable prompts, see:
references/prompt-templates.md