メニュー
Explain code diffs in Markdown, one changed file at a time. Use when user asks to explain unstaged changes, staged changes, a commit, commit range, branch diff, PR diff, or pasted diff. Ask for diff source when missing.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
Analyze a list of open questions and suggest up to three answers for each. Use when the user wants options, recommendations, or help resolving multiple unanswered questions.
Deliver a PRD through orchestrated task decomposition, implementation agents, and independent QA. Use when every acceptance criterion must be verified before completion.
Explain changes made yesterday as a simple list. Use when user asks what changed yesterday, what was implemented yesterday, or needs a non-technical change summary from recent git work.
Pressure-test, reduce, and rewrite prompts for GPT-5.5. Use when the user asks to grill, audit, critique, harden, improve, optimize, simplify, de-noise, or rewrite a prompt, system prompt, developer instruction, agent playbook, or tool-use workflow specifically for GPT-5.5; especially when it may contain no-op instructions, contradictions, vague rules, missing success criteria, missing output rules, missing validation, unsupported claims, or unclear stop rules.
Build shared understanding before action by interviewing the user about ambiguous implementation, product, planning, or design tasks. Use when goal, scope, constraints, risks, success criteria, done state, or next action are unclear; when user wants a thinking partner; or when user needs a handoff-ready task prompt. Do not write PRDs; use to-prd for product requirements.
Detect sloppy-code signals with repo-wide search metrics and sampled evidence. Use when asked to audit codebase quality, "vibe coding", `isRecord`, broad `Record<string, unknown>` guards, fallback usage, excessive null guards, non-null assertions, unsafe type assertions, `node:*` imports in browser/shared code, swallowed errors, TODO debt, or code smell hotspots before refactoring.
SOC 職業分類に基づく
| name | explain-diff |
| description | Explain code diffs in Markdown, one changed file at a time. Use when user asks to explain unstaged changes, staged changes, a commit, commit range, branch diff, PR diff, or pasted diff. Ask for diff source when missing. |
Explain what changed in each changed file.
Sort by dependency flow:
Within same layer, explain files that clarify other files first. If still tied, use path order.
git diffgit diff --stagedgit show --stat --patch <commit>git diff <base>...<head>Use TEMPLATE.md.