changelog-gen
Skill1 starsChanged 6 months agoMITView on GitHub
Build a CHANGELOG.md from conventional commits. Groups by type (feat, fix, perf...) and infers semver bump.
- Reads credentials
6 other projects use a version of this.
Adopted by
Most recently taken up by
- laolaoshiren/claude-code-skills-zhtheir own version, first seen Nov 10, 2026
- jholhewres/devclaw-skillstheir own version, first seen Oct 9, 2026
- cataclysmbnteam/Cataclysm-BNtheir own version, first seen Oct 9, 2026
- cataclysmbn/Cataclysm-BNtheir own version, first seen Oct 8, 2026
- trac3r00/agent-skillstheir own version, first seen Aug 26, 2026
- sergeeey/Claude-cod-top-2026their own version, first seen May 13, 2026
Other versions6 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 6
- cataclysmbn/Cataclysm-BN★ 1.3ksame name
- cataclysmbnteam/Cataclysm-BN★ 1.3ksame name
- laolaoshiren/claude-code-skills-zh★ 910same name
- sergeeey/Claude-cod-top-2026★ 9same name
- jholhewres/devclaw-skills★ 4same name
- trac3r00/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 repository5 other files it gives its agents.
- api-mockSkill
- db-migrateSkill
- i18n-translateSkill
- license-checkSkill
- security-auditSkill
The file
We split this skill into the rules it gives an agent
5 rules. 0 are common, 3 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
3
Distinctive
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 22
All time: full history (rare.
- Distinctive: line 24
If git describe fails (no tags), this is the first release — say so.
- Very specific: line 82
If a CHANGELOG.md exists, prepend the new section above the most recent release.
- Distinctive: line 83
If not, create one with a "Keep a Changelog" header.
- Very specific: line 90
If package.json exists: npm version <bump> --no-git-tag-version
“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
Changelog Generation Skill
You are generating a CHANGELOG entry from git history.
Step 1 — Pick the range
Ask (or infer):
- Since the last tag:
git log $(git describe --tags --abbrev=0)..HEAD - Since a specific tag:
git log v1.2.0..HEAD - All time: full history (rare; only for first release)
If git describe fails (no tags), this is the first release — say so.
Step 2 — Parse conventional commits
Recognized prefixes:
feat:/feat(scope):→ Featuresfix:/fix(scope):→ Bug Fixesperf:→ Performancerefactor:→ Refactorsdocs:→ Documentationtest:→ Testsbuild:/ci:→ Build & CIchore:→ Chore (often omitted from changelog)revert:→ Reverts
Breaking changes:
- Footer
BREAKING CHANGE:or!after type (e.g.,feat!:) - These get a 🚨 prefix and forces a major bump
Step 3 — Infer semver bump
| Commits found | Bump |
| Any BREAKING CHANGE | MAJOR |
Any feat: (no breaking) | MINOR |
Only fix:, perf:, refactor:, docs:, etc. | PATCH |
Only docs:, chore:, test: | No release recommended |
Step 4 — Write the CHANGELOG
Format:
## [1.4.0] — 2026-05-22
### 🚀 Features
- **auth**: support OAuth via GitHub (#142)
- **dashboard**: add export-to-CSV button (#138)
### 🐛 Bug Fixes
- **api**: handle 429 from upstream gracefully (#145)
### ⚡ Performance
- **db**: index `users.email` (#147) — login query 12× faster
### 🚨 Breaking Changes
- **config**: rename `API_KEY` → `OPENAI_API_KEY` (#150)
Migration: rename your env var. See UPGRADE.md.Each entry:
- Includes the scope if present
- Links the PR or commit hash
- Strips the conventional prefix (no
feat:in the bullet itself) - Has a one-line description — full PR title
Step 5 — Update CHANGELOG.md
If a CHANGELOG.md exists, prepend the new section above the most recent release.
If not, create one with a "Keep a Changelog" header.
Step 6 — Suggest next steps
Print:
- New version:
<computed> - Suggested tag:
git tag -a vX.Y.Z -m "Release vX.Y.Z" - If
package.jsonexists:npm version <bump> --no-git-tag-version
When NOT to use
- Commits don't follow conventional commits — recommend
cz-commitlintsetup first - The user wants release notes in a totally different format (e.g., for marketing)
Failure modes
- ⚠️ Squash-merged PRs may lose individual commit messages. The PR title becomes the commit. That's usually fine.
- ⚠️ If a commit message is just
fix: stuff, flag it — recommend amending.
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.

