Changelog and versioning
SkillDocs & knowledgeCreates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes.
Available today. Use it from your connected AI after setup.
No other account needed.
Connect ahel once, and every AI you use reads what you have installed.
Then ask your AI: use the Changelog and versioning skill
What this skill tells your AI
The instructions your AI receives, as published by stijnvanhulle/template in .agents/skills/changelog/SKILL.md and read by ahel’s review.
Turn technical git commits into user-facing changelog entries. This monorepo uses Changesets for versioning and builds the changelog from changeset entries.
When to use
- Preparing release notes for a new version
- Documenting changes for the website or docs pages
- Keeping a consistent writing style across release notes
How it works
- Scan git history for the relevant range.
- Categorize commits (features, improvements, bug fixes, breaking changes) and filter noise (refactor, test, chore).
- Translate developer commits into customer-facing language.
- Format entries per the repo conventions.
References
| Reference | Covers |
|---|---|
| format.md | docs/changelog.md structure, change-type sections, and examples |
Related skills
| Skill | Use for |
|---|---|
| changeset | Writing the changeset a release note comes from |
| documentation | Documentation style for changelog entries |
Checklist
- Code changes have matching documentation updates
- Changeset added via
pnpm changesetfor code changes - Changelog updated in
docs/changelog.md
Resources
- Changesets: https://github.com/changesets/changesets
- VitePress markdown extensions: https://vitepress.dev/guide/markdown
Signals
- GitHub stars
- 34
- Last commit
- Sep 2026
Advanced
- Catalog kind
- skill
- Gateway key
changelog-stijnvanhulle- Source
- github.com/stijnvanhulle/template