repo-changelog
Skill0 starsChanged 23 days agoMITView on GitHub
Generate end-user friendly release notes and changelogs from actual git diffs, consolidating related changes and identifying upgrade steps. Use for CHANGELOG.md updates, release summaries, or Slack release notes.
In this repository11 other files it gives its agents.
- AGENTS.mdAGENTS.md
- library/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- cavecrewSkill
- councilSkill
- herdrSkill
- humanizerSkill
- specsmdSkill
- caveman-commitSkill
- cavemanSkill
- project-flowSkill
The file
We split this skill into the rules it gives an agent
11 rules. About 0 are common, 11 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈11
Distinctive · estimate
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
- could be automatic: a setting could enforce it
- Distinctive: line 8
Read actual code and documentation diffs.
- Distinctive: line 25
Read the full relevant diffs, including removed behavior, settings, documentation, and tests.
- Distinctive: line 27
Check claims against the final code.
- Distinctive: line 34
Never claim live behavior was tested when only offline checks ran.
- Distinctive: line 35
Never include secrets, private service addresses, or credentials.
- Distinctive: line 39
Update the repository's existing changelog if present.
- Distinctive: line 50
Use one line per bullet where practical.
- Distinctive: line 53
When repository rules require a changelog update on every commit, add an accurate entry for each commit's own changes.
- Distinctive: line 59
Use the host's Git and filesystem tools directly.
- Distinctive: line 62
No extra dependency is needed for this workflow.
- Distinctive: line 64
Before finishing, check every release bullet against the comparison diff, remove duplicates and technical implementation details, and …
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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
Release notes and changelog
Read actual code and documentation diffs. Describe the final result for users, rather than repeating commit subjects or internal implementation details.
Choose the comparison
Honor the requested repository and range: two tags, changes since a tag, a branch such as main, or the last N commits. Default to the current repository and 50 commits only when no range was given. Detect the remote without requiring GitHub; Bitbucket and local repositories work too.
For a pre-commit request, include the working tree and relevant untracked files, and label the notes Unreleased. State which local reference was used if local and remote branch references differ. Do not silently fetch, push, publish, or commit unless the user authorized that action.
Read and consolidate
- Read the full relevant diffs, including removed behavior, settings, documentation, and tests. Commit messages are context, not evidence.
- Check claims against the final code. Merge related changes; omit intermediate rewrites, reversals, and changes with no net effect.
- Describe what users can do, what works differently, and what they must change when upgrading. Avoid function names, variable names, and jargon in release bullets. Link to setup documentation for exact settings.
- Flag breaking changes that require user action, such as new login requirements, incompatible saved data, or renamed client commands.
- Never claim live behavior was tested when only offline checks ran.
- Never include secrets, private service addresses, or credentials.
Write the notes
Update the repository's existing changelog if present. Preserve released history and use its established order and headings. Use brief Markdown bullets suitable for documentation or Slack. Include only relevant groups:
- New Features
- Enhancements
- Bug Fixes
- Changes
- Breaking Changes
- Others (including documentation)
Use one line per bullet where practical. Add short notes or links for setup and known limitations. Do not invent a release version or date.
When repository rules require a changelog update on every commit, add an accurate entry for each commit's own changes. Do not substitute unrelated wording edits merely to touch the file.
Tools and checks
Use the host's Git and filesystem tools directly. The supplied skill description names optional analyzer/formatter scripts, but their source was not supplied; this installation does not claim to bundle them. No extra dependency is needed for this workflow.
Before finishing, check every release bullet against the comparison diff, remove duplicates and technical implementation details, and verify that upgrade instructions describe the final state.
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.

