check-changes
Skill4 starsChanged 16 days agoApache-2.0View on GitHub
Use when the user asks to write, update or check the changelog or
In this repository10 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- bump-versionSkill
- check-changesSkill
- check-versionSkill
- crit-cliSkill
- critSkill
- crit-storySkill
- bump-versionSkill
- check-versionSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 3 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 14
Write files, comments and reports in English, ASCII only.
- Distinctive: line 15
Use simple English: short sentences, common words, simple grammar.
- Very specific: line 25
Run uv --version. If it fails, stop and ask the user to install uv: https://docs.astral.sh/uv/getting-started/installation/
- Very specific: line 33
Read the comment at the top of CHANGES.md.
- Distinctive: line 49
Run the check. It enforces the limits:
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Check the changelog
Communication
- Reply in the language the user writes in.
- Write files, comments and reports in English, ASCII only.
- Use simple English: short sentences, common words, simple grammar.
Models
- The current model does all of it. Deciding what a user would notice takes
judgement, so prefer
opuson Claude orgpt-6.1-solon Codex, high effort. If a model is not available, use the current one.
Before you start
- Run
uv --version. If it fails, stop and ask the user to install uv: https://docs.astral.sh/uv/getting-started/installation/ - A sandbox can stop uv from writing its cache. If a later
uv runreports that, set the variableUV_CACHE_DIRto.cache/uv, which git ignores, and run it again. Do not call Python directly, and do not check the limits by hand instead.
Steps
- Read the comment at the top of
CHANGES.md. Its rules decide what goes in. Find the last release: the newest commit whose message starts with
release:, or the newestv*tag. List the commits since then:git log --oneline <last release>..HEAD- For each commit, decide if a user would notice it. A fix needs an entry only if a released version had the bug: check that before you report a gap.
- Compare with
## Development. Report what is missing, and any entry for something that no longer exists. Add or correct entries if the user asked for that. Merge related entries instead of adding a long one. Run the check. It enforces the limits:
uv run scripts/version/version.py checkExample of a failure:
CHANGES.md:51: bullet has 170 characters, the limit is 160. Shorten the entry or link to the docs. Never change a limit to make an entry fit.
Done when
version.py checkexits with 0, and every commit that a user would notice has an entry in## Development.
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.

