About changelog
A repository skill describing how release-please creates and publishes a CHANGELOG.md from conventional commits. It helps maintainers understand eligible entries, release pull requests, and how to investigate missing notes.
Key features
- 01Maps commit types to changelog sections
- 02Explains release-please generation steps
- 03Lists commands to inspect release notes
- 04Documents checks for missing entries
Use cases
- 01Check why a commit is absent from the changelog
- 02Preview notes in an open Release PR
- 03Find published GitHub Release notes
Install
Copy the command and run it in a terminal.
$
npx skills add https:/ / github.com/ motormetrics/ motormetrics --skill changelogAfter installing, type/changelogin Claude Code to confirm it loaded.
Details
From the project READMEChangelog Skill
CHANGELOG.md is generated by release-please as part of each Release PR.
How It Works
- release-please runs on push to
main - It generates notes from conventional commits since the last release
- The notes are prepended to
CHANGELOG.mdin the open Release PR - Merging the Release PR commits the changelog and publishes the same notes as the GitHub Release
Changelog Sections
Commit types map to changelog sections:
| Commit Type | Changelog Section |
|---|---|
feat | Features |
fix | Bug Fixes |
perf | Performance Improvements |
revert | Reverts |
feat! / BREAKING CHANGE | ⚠ BREAKING CHANGES |
Types chore, docs, refactor, test, ci, build and style do not appear in the changelog.
Viewing Changelog
# View the changelog file
cat CHANGELOG.md
# View a specific GitHub release's notes
gh release view v5.31.0
# Preview the next entry in the open Release PR
gh pr list --label "autorelease: pending"
Missing Changelog Entry?
- Check the commit type: only
feat,fix,perfandrevertgenerate entries - Verify the commit landed on
main - Check the Release PR has been updated:
gh run list --workflow=release.yml - Ensure the commit message follows the conventional format
File Location
- Changelog:
CHANGELOG.md(root of repository) - Config:
release-please-config.json
Related
- See
release-managementskill for release workflow
Comments
Markdown supported