メニュー
Summarizes uncommitted git changes and flags anything risky. Use when the user asks what changed, wants a commit message draft, or asks to review their diff before committing.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| title | summarize-changes |
| name | summarize-changes |
| description | Summarizes uncommitted git changes and flags anything risky. Use when the user asks what changed, wants a commit message draft, or asks to review their diff before committing. |
!git diff HEAD
Summarize the changes above in two or three bullet points. Focus on the logical intent of the changes, not the line-by-line diff.
Then list any risks you observe, such as:
If the diff is empty, say there are no uncommitted changes.
Note for learners: the ! backtick line above is dynamic context injection. When Claude Code activates this skill, it runs git diff HEAD and replaces that line with the real diff output before Claude reads the file. The result is that Claude sees the actual diff as part of the skill body, without needing a separate tool call. This is the canonical example from the Claude Code skills documentation.
Explains code in plain language for someone unfamiliar with the programming language. Use when asked to explain code, walk through logic, describe what a function does, or when the user says "explain this" or "walk me through this".
Summarizes uncommitted git changes in a concise machine-readable format. Use in CI pipelines, scripts, or headless invocations where the output will be piped or captured.
Explains what a skill is and demonstrates that skills are working. Use when testing skills, when asked about skills, or when asked to demonstrate how skills work.
Demonstrates the personal scope for Claude Code skills. Use when testing personal-scoped skills or when the user wants to understand the difference between personal and project skill scopes.
Lists the conventions for this project and demonstrates the project scope for Claude Code skills. Use when asked about project conventions, code style, or as a demonstration of project-scoped skills.
Draft a CHANGELOG.md entry for the current changes in Keep a Changelog format. Use when releasing, tagging a version, or updating CHANGELOG.md.
