Git summarize changes

Skill evindunn/ai-skills/git-summarize-changes

Skills for AI agents

Install

npx -y skills add evindunn/ai-skills --skill git-summarize-changes

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

0 stars0 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.

What its author says it does

Copied from the file, not written here

Summarize current-branch changes vs an auto-discovered base branch for MR-style output. Use when the user asks to summarize git changes, draft an MR description, or compare against main/release.

SKILL.md

1.3 KB, as published. Nobody here has run it

Git Summarize Changes

Produce a concise summary from <base_branch>..HEAD as the source of truth.

Base branch

User-specified base branch, if given.
Else default remote branch:

BASE_BRANCH="$(git symbolic-ref --short refs/remotes/origin/HEAD 2>/dev/null | sed 's|^origin/||')"

If empty, ask the user for a base branch.

Workflow

Run from repo root; validate branch and range from git (do not trust stale chat).
Reuse chat context only if it matches current <base_branch>..HEAD.
Draft markdown; copy to clipboard when possible; paste the same in chat.

Validate

git rev-parse --verify "$BASE_BRANCH" >/dev/null
git rev-parse --abbrev-ref HEAD
git log --oneline "$BASE_BRANCH"..HEAD
git diff --stat "$BASE_BRANCH"...HEAD

Empty range: say so; do not invent a summary.

Output template

## Summary
- <2-5 bullets on intent and impact>

Clipboard (macOS)

cat <<'EOF' | pbcopy
## Summary
- <final bullets>
EOF

If pbcopy fails, retry with needed permissions and still paste the markdown in chat.

Gives 0 of the 12 instructions most pr commit review skills give

Counted across 888 of the 1,342 authors here whose files we hold, read 2026-08-06

use conventional commits formatin 123 of 888, across 110 files
keep subject line under 72 charactersin 60 of 888, across 46 files
delete branches after mergein 50 of 888, across 37 files
use imperative mood in subject linein 50 of 888, across 41 files
use imperative mood in commit messagesin 45 of 888
generate a conventional commit messagein 42 of 888
make atomic commitsin 37 of 888, across 25 files
run tests before committingin 36 of 888, across 24 files
run project test suite to verify clean baselinein 35 of 888, across 7 files
run detected project setup commandsin 34 of 888, across 6 files
wrap commit body at 72 charactersin 32 of 888, across 25 files
split unrelated changes into separate commitsin 32 of 888, across 27 files

Said here and by no other author read

use base branch to head as source of truth
use user-specified base branch if provided
reuse chat context only if it matches range
copy markdown summary to clipboard
paste markdown summary in chat

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once.