Diff Explain
Use when you want a one-paragraph plain-English summary of what a diff does. Activates on "summarize this diff", "what does this PR do", "explain this branch", or when pointed at a PR URL or local branch.
Install
$ agentstack add skill-sagargupta16-claude-skills-diff-explain ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-sagargupta16-claude-skills-diff-explain) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
diff-explain
Live context (when diffing a local branch)
- Current branch diff stat: !
git diff $(git merge-base HEAD origin/main 2>/dev/null || git merge-base HEAD main 2>/dev/null || echo HEAD)...HEAD --stat 2>/dev/null || echo "no local diff vs main"
When to activate
- User pastes a diff and asks "what does this do?" / "summarize" / "explain".
- User shares a PR link or branch name and wants a quick read before reviewing.
- Reviewing unfamiliar changes before merge.
Do NOT activate when the user is asking for a detailed line-by-line review -- that's a different task.
Steps
- Get the diff.
- PR link:
gh pr diff - Local branch:
git diff ...HEAD(default base:mainormaster) - Pasted: use what the user pasted.
- Read it fully. Don't skim the first 50 lines and guess.
- Group by concern. Even if the diff touches many files, most diffs have 1-3 concerns (a bug fix, a rename, a new feature). Name each concern in plain language.
- Write ONE paragraph. 3-5 sentences covering:
- What changed (the concern, not the files).
- Why it likely changed (if the commit message / PR title / linked issue says).
- What risk it introduces (behavior change, API change, DB migration, dependency bump).
- Optional risk line. If one specific thing deserves attention before merge, append one line starting with
Watch out for:.
Rules
- No file-by-file walk. Group by concern, not by path.
- No bullet lists. Prose only.
- If the diff is large (>500 lines), say so in the first sentence and narrow to the top 2-3 concerns instead of trying to cover everything.
- Don't speculate about business motivation beyond what commits, PR title, or linked issue state.
- Flag real problems. Suspected bugs, security issues, missing tests, or breaking API changes go in the summary or in the "Watch out for" line. Don't paper over them.
Output
One paragraph. Optional single-line Watch out for: ... trailer.
No preamble ("Here's a summary of..."). Lead with the answer.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: Sagargupta16
- Source: Sagargupta16/claude-skills
- License: MIT
- Homepage: https://sagargupta.online
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.