git-summary
Skill4 starsChanged 16 days agoMITView on GitHub
Summarise what's happened on the current branch so far — commits, uncommitted work, untracked files, and how it diverges from the default branch — as bullet points. Use when the user asks what's on this branch, what's changed, where things are up to, to recap or catch up on the branch, or for a git status, diff, or branch summary.
6 other projects use a version of this.
Adopted by
Most recently taken up by
- nieyuanqing/software-engineering-skillstheir own version, first seen Oct 11, 2026
- RussBrown00/agent-skillstheir own version, first seen Jul 30, 2026
- tinyhumansai/skill-registrytheir own version, first seen Jun 7, 2026
- csteamengine/skillstheir own version, first seen May 21, 2026
- erdcpatel/agent-skillstheir own version, first seen Apr 19, 2026
- kunwl123456/zeroclaw-skills-collectiontheir own version, first seen Feb 19, 2026
Other versions6 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 6
- kunwl123456/zeroclaw-skills-collection★ 27same name
- tinyhumansai/skill-registry★ 5same name
- nieyuanqing/software-engineering-skills★ 4same name
- RussBrown00/agent-skills★ 1same name
- csteamengine/skills★ 0same name
- erdcpatel/agent-skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository7 other files it gives its agents.
- artifact-conventionsSkill
- commitSkill
- discussSkill
- merge-fromSkill
- recallSkill
- rememberSkill
- translate-filesSkill
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 5 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 23
Read the diffs of anything whose purpose isn't obvious from the file name.
- Distinctive: line 39
No commit SHAs unless a specific commit needs pointing at.
“Common” is measured: kept by at least 6 in 10 of the 5 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Context
Detect the default branch via git symbolic-ref refs/remotes/origin/HEAD (fall back to main, then master), then:
git branch --show-current
git status --short
git log --oneline <default>..HEAD
git diff --stat <default>...HEAD
git diff HEAD --statRead the diffs of anything whose purpose isn't obvious from the file name.
Task
Summarise the branch as bullets, grouped under these headings. Skip a heading with nothing under it.
- Branch — name, and how far ahead/behind the default branch.
- Committed — what the commits on this branch actually accomplish, grouped by purpose rather than listed commit by commit.
- Uncommitted — staged and unstaged work in progress, by purpose.
- Untracked — new files, and whether they look intentional or incidental.
- Loose ends — anything that looks unfinished, contradictory, or accidentally included: debug code, a half-applied rename, an unrelated file, a stray artefact.
Style
- One line per bullet. Say what changed and why, not which files.
- Reference paths only when they identify the thing being described.
- No commit SHAs unless a specific commit needs pointing at.
- Report only what the commands show. If the branch is empty or clean, say that in one line rather than padding the summary.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.