# Changelog

> Turn commit history and changesets into user-facing release notes.

- Skill: `stijnvanhulle/changelog` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add stijnvanhulle/changelog`
- Raw SKILL.md: https://api.skillmd.com/api/skills/stijnvanhulle/changelog/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: stijnvanhulle (https://skillmd.com/u/stijnvanhulle)
- Updated: 2026-09-22
- Page: https://skillmd.com/skills/stijnvanhulle/changelog

---


# Changelog and versioning

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

1. Scan git history for the relevant range.
2. Categorize commits (features, improvements, bug fixes, breaking changes) and filter noise
   (refactor, test, chore).
3. Translate developer commits into customer-facing language.
4. Format entries per the repo conventions.

## References

| Reference | Covers |
| --- | --- |
| [format.md](references/format.md) | `docs/changelog.md` structure, change-type sections, and examples |

## Related skills

| Skill | Use for |
| --- | --- |
| [changeset](../changeset/SKILL.md) | Writing the changeset a release note comes from |
| [documentation](../documentation/SKILL.md) | Documentation style for changelog entries |

## Checklist

- [ ] Code changes have matching documentation updates
- [ ] Changeset added via `pnpm changeset` for code changes
- [ ] Changelog updated in `docs/changelog.md`

## Resources

- Changesets: https://github.com/changesets/changesets
- VitePress markdown extensions: https://vitepress.dev/guide/markdown