explain-changes
Skill1 starsChanged 6 days agoApache-2.0View on GitHub
Explain commits, pull requests, branches or a diff in the reader's language — what changed, why, impact on results, documentation and contracts. Use when the maintainer or a contributor asks to review or understand changes, for example in Italian.
4 other projects use a version of this.
Adopted by
Most recently taken up by
- ahmadammarm/musyskillstheir own version, first seen Nov 8, 2026
- elie222/inbox-zerotheir own version, first seen Oct 8, 2026
- gregwebs/skills-sdlctheir own version, first seen Sep 29, 2026
- ernesto27/skillstheir own version, first seen Jun 21, 2026
Other versions4 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 4
- elie222/inbox-zero★ 13ksame name
- gregwebs/skills-sdlc★ 20same name
- ahmadammarm/musyskills★ 1same name
- ernesto27/skills★ 1same 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 repository39 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- add-methodSkill
- adr-newSkill
- commitSkill
- explain-changesSkill
- fix-ciSkill
- golden-caseSkill
- implement-specSkill
- onboardingSkill
- plan-sprintSkill
- pre-prSkill
- pr-triageSkill
- releaseSkill
- roadmap-updateSkill
- run-sprintSkill
- session-endSkill
- session-startSkill
- spec-newSkill
- translateSkill
- add-methodSkill
- adr-newSkill
- commitSkill
- fix-ciSkill
- golden-caseSkill
- implement-specSkill
- onboardingSkill
- plan-sprintSkill
- pre-prSkill
- pr-triageSkill
- releaseSkill
- roadmap-updateSkill
- run-sprintSkill
- session-endSkill
- session-startSkill
- spec-newSkill
- translateSkill
- fairmarkSkill
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 1 is distinctive, and 1 is very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 10
Read the commits and the diff.
- Very specific: line 12
Write the explanation in the requested language (default: the language of the request.
“Common” is measured: kept by at least 6 in 10 of the 3 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
<!-- Generated from .agents/skills/explain-changes/SKILL.md by scripts/sync_agents.py. Edit the source, not this file. -->- Identify the scope: a commit range (
git log A..B), a PR (gh pr view N,gh pr diff N), a branch versusmain, or the working tree. - Read the commits and the diff. Group changes by area: core methods, adapters, tests and golden cases, schemas, documentation, tooling and CI.
- Write the explanation in the requested language (default: the language of the request;
for the maintainer see
CLAUDE.local.md):- one-paragraph summary;
- per area: what changed and why, citing files;
- impact: numerical changes (golden cases,
method_version), schema changes (additive or breaking), documentation and translations to update, risks; - questions or decisions for the reviewer.
- Quote commit subjects and code identifiers in their original English. No icons or emoji.
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.