diff-recap

Converts a git diff into a PR-pasteable per-file change recap with git-attested line counts.

14|1|Updated Jun 14, 2026
One-click install
npx skills add https://github.com/allemaar/open-skills --skill diff-recap-allemaar
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: diff-recap
Source: https://github.com/allemaar/open-skills/tree/main/skills/diff-recap
Command: npx skills add https://github.com/allemaar/open-skills --skill diff-recap-allemaar

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Writing a pull request summary by hand means re-reading the diff and manually counting changes, which invites errors and unverifiable numbers. This Skill turns a git diff into a reviewer-ready recap whose per-file paths, statuses, and line counts are transcribed verbatim from git diff --numstat, so the headline totals always equal the sum of the rows. ## Core Features & Use Cases - True-by-construction recap: Per-file path, status, added, and removed values come straight from git; the model writes only the labels and groupings, and a bundled value gate rejects any record whose totals drift from its rows. - Triple output bundle: Emits a diff-recap/1 YON record, a PR-pasteable markdown summary, and an information-complete ASCII twin (plus an optional widget on Claude Code), with no hosted service dependency. - Fail-closed behavior: No git source or an empty diff produces an honest NO DIFF card with gate_status=barren instead of a fabricated recap. - Use Case: Before opening a pull request, run it on your branch to get a grouped change table (feature/tests/docs) with git-attested counts you can paste directly into the PR description, then hand the same change-set to a cold review. ## Quick Start Ask the agent to recap the changes in the current branch with /diff-recap and paste the resulting summary into your pull request.

Frequently Asked Questions about diff-recap

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate a PR summary from a git diff?

Invoke /diff-recap with a range (defaulting to the working tree against HEAD, an A..B range, or --staged) and an intent describing the PR's goal. It runs git diff --name-status and --numstat, groups files by area, and emits a paste-ready markdown table plus an ASCII twin.

How does diff-recap keep the change counts accurate?

Per-file path, status, added, and removed values are transcribed verbatim from git diff --numstat; the model writes only labels and groups. A bundled value gate (diff-recap-check.mjs) rejects any record whose headline totals do not equal the sum of its rows, and can cross-check rows against the real numstat.

What is the difference between diff-recap and orient-map or orient-status?

orient-map shows the shape and delta of the work and orient-status reports position and ETA, while diff-recap recaps what a concrete change-set contains for a reviewer. It is also not a code review; it summarizes what changed without judging quality.

Does diff-recap work without Claude Code or a visualization tool?

Yes. The information-complete ASCII twin is always emitted and is the only render in runtimes without the visualize tool, and agent consumers receive the YON record only. It has zero external or hosted dependencies beyond git itself.

What happens when there is no diff or no git repository?

It fails closed: the record sets gate_status to barren and attested to false, carries no file rows, and renders a NO DIFF card instead of fabricating a recap. A clean verdict requires attested=true from a real git source.