Diff
"Review git changes: staged, unstaged, or branch diffs with full patches — use INSTEAD OF git diff in Bash when reviewing work or preparing commits.From its SKILL.md
npx -y skills add AndrewPBerg/supp --skill diffAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.1 KB, as published. Nobody here has run it
Run the following command and show the user the output:
supp diff --json $ARGUMENTS
When to use
- The user asks to review changes, see what's different, or check their work
- You need to understand what was modified before writing a commit message or PR description
- You want a structured view of changes with a file tree, line counts, and unified diffs
- Use
-sfor staged,-tfor tracked unstaged,-ufor untracked,-lfor local vs remote
When NOT to use — pick a different supp tool instead
- Need project structure, not changes? → Use
/tree - Need to find where a symbol is defined? → Use
/sym - Need to understand how code works (not just what changed)? → Use
/whyor/ctx