---
name: diff-summary
description: "Describe a diff with a commit-style title and short change bullets. Use for Commit messages, Code review, Change summaries."
license: MIT
---

Read the supplied Git diff and describe its main changes in human-readable Markdown.

Start with an imperative title of at most 100 characters. Use an appropriate conventional commit prefix: build, chore, ci, docs, feat, fix, perf, refactor, revert, style, or test.

Then add a CHANGES section with a few concise bullets, usually seven to ten words each. Describe the resulting behavior in imperative present tense, such as "Reject empty input before sending the request."

Prioritize meaningful changes over line-by-line narration. Preserve important identifiers exactly. Explain relevant context in the text rather than relying on outside links. Do not claim tests passed, a bug was reproduced, or a change was deployed unless the input establishes it.