Skip to content

commandWorkflow

Summarize Diff

Explains a diff in plain language for a product manager or support lead: what changed, who is affected and what could go wrong.

npx workspacetemplates add summarize-diff --tool claude-code

Writes 1 file to .claude/commands/

.claude/commands/summarize-diff.md20 lines · 1.2 KBFile
---
description: "Explains a diff in plain language for a product manager or support lead: what changed, who is affected and what could go wrong."
argument-hint: "[branch, commit range or pull request number]"
---

Summarize a code change for a non-engineer. Target: $ARGUMENTS (current branch against main if empty).

1. Get the change: a range through `git diff <base>...<head>`, a commit with `git show`, or a pull request with `gh pr diff <n>`. Read the commit messages too.
2. Work out what a user or customer would notice. Look at UI text, endpoints, emails, pricing logic, permissions, data stored, and defaults. Ignore pure refactors, but say they exist.
3. Write for someone who has never seen the code: no file names, no function names, no acronyms without a short explanation.

Format:
**In one sentence**
**What changes for users** (bullets, plain words)
**Who is affected** (which customers, roles or plans)
**Risks and what to watch** (support load, data changes, rollout order)
**Needs a decision** (anything the code leaves open)
**Not covered** (what you could not tell from the diff)

Keep it under 200 words. Never guess a business reason; if the diff does not show it, say so. Make no changes.

What it does

Engineers write for engineers, and a pull request description full of function names tells a product manager nothing. This command reads the change and describes it by its effect on users and the business.

It avoids jargon, says when something is a risk and flags anything it could not understand from the code alone.

Example

you › /summarize-diff 482

agent › In one sentence: customers can now pause a subscription for up to 3 months. Affected: paying monthly plans only. Risk: paused accounts keep their data but lose API access, so support may get questions. Not covered: whether annual plans should pause too.

Questions

Does it include code in the summary?
No. The output is written for readers who do not code, with technical terms explained or left out.
What if the diff is huge?
It groups changes by their effect on users and says which parts it skimmed.
  • Debug Error

    CommandWorkflow

    Free
  • Estimate Task

    CommandWorkflow

    Free
  • Explain Code

    CommandWorkflow

    Free
  • Plan Feature

    CommandWorkflow

    Free