clean-git-summary
Skill1 starsChanged 7 days agoMITView on GitHub
Summarize a git diff in a short 3-block technical format. Use before a commit, for a PR description, or when asked what changed.
In this repository7 other files it gives its agents.
- angular-conventionsSkill
- appstore-payouts-to-excelSkill
- conventional-commitSkill
- create-commitSkill
- invoice-processingSkill
- ksef-invoiceSkill
- xlsx-toolkitSkill
The file
Files
Clean Git Summary
- Pick the diff: staged (
git diff --cached), else working tree (git diff), else<base>...HEADif a base was given. Start withgit diff --stat. - Skip lockfiles, generated and minified files unless the change in them is intentional.
- Describe behavior and structure, not line edits. Group by module when many files changed.
- Output exactly this, 3–6 bullets in total:
### Changes
- Primary behavior or architecture change.
### Scope
- `path/to/module/`: what changed there.
### Risk
- Breaking: none | <contract that changed>
- Migration: none | <step needed>Rules: imperative tone ("Add endpoint"), no preamble, no adjectives, no AI mentions. Read-only — never stage or commit.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
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.