Summary
Summarize the most recent commit or pending changes — what they do, how they fit into the existing code, and a diagram if the change is structural.From its SKILL.md
npx -y skills add bitfootco/bender --skill summaryAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 2 stars2 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
3.2 KB, as published. Nobody here has run it
Change Summary
Core Rule
EXPLAIN WHAT THE CHANGE SHIPS AND HOW IT FITS — NOT WHAT FILES MOVED OR WHAT LINES CHANGED.
The output should let someone who hasn't touched the code in a week immediately understand what the change is, why it matters, and how it connects to the existing system. Keep it short enough to read in under 30 seconds.
Phase 1: Determine scope
Run these in order and use whichever produces output first:
git diff HEAD— unstaged working tree changesgit diff --cached— staged-only changesgit show HEAD— most recent commit
If none of these produce output (brand-new repo with no commits), say so and stop.
Phase 2: Gather context
- Get the file-level summary:
git diff --stat HEAD(orgit show --stat HEADif falling back to the commit) - Read the full diff — every line of it
- For each file that changed substantially, read the surrounding code in that file: the functions, classes, or modules adjacent to the changed lines. Don't read only the diff lines — understand what the changed code lives inside and connects to.
- If there's a
README.md,CLAUDE.md, orROADMAP.mdat the project root and the change seems architectural, skim it for context on the project's structure and intent.
Goal: understand not just what changed but what role those changes play in the larger codebase.
Phase 3: Produce the summary
Write the output directly — no preamble, no sign-off, no "Here is your summary:".
Format
**[One-line title — the change in plain English]**
[2–3 sentences: what it does and why. Lead with the behavior or capability, not the mechanism.]
[1–2 sentences: how it connects to the existing code — what it replaces, extends, calls into, or is called by.]
[Diagram OR key details — see below]
Diagram vs. prose
Use a Mermaid diagram when the change involves any of:
- Data or control flow between components
- A new call chain or middleware layer
- New wiring between modules (a new service, handler, hook, or event listener)
- Relationships between the new code and multiple existing parts of the system
Use bullet points for contained changes:
- Bug fixes
- Config or constant updates
- Single-function additions with no architectural implications
- Copy or text changes
Diagram rules:
- Mermaid only — no ASCII art
- 4–8 nodes maximum
- Label every edge to show what flows or what triggers what
- Show only what the change introduces or touches — not the whole system
- Use
graph LRfor flows,sequenceDiagramfor call sequences
Bullet rules:
- 3–6 bullets maximum
- Each bullet is a behavior or consequence, not a file name or line number
Hard Rules
- Target 10–20 lines of output. Never exceed 30.
- No file names, line numbers, or "this was modified in X" narration.
- No padding. Short changes get short summaries.
- If the diff doesn't make the intent obvious, describe what it does — don't invent a "why."
- No questions. No asking for clarification. Run the commands, read the code, write the summary.