Help us improve
Share bugs, ideas, or general feedback.
From gh-guard
Generates automated changelogs for Rust projects from conventional commits using git-cliff. Integrates with cargo-release, release scripts, and GitHub Actions for release notes.
npx claudepluginhub sbom-tool/gh-guardHow this skill is triggered — by the user, by Claude, or both
Slash command
/gh-guard:changelogThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Automated changelog generation from conventional commits, integrated with the release workflow.
Automates changelog generation from Git commits, PRs, and releases in Keep a Changelog format using Conventional Commits and Semantic Versioning for release workflows.
Generates Markdown changelogs from git commits, parsing conventional types, suggesting semantic versions, and using Keep a Changelog format with breaking change highlights.
Generates and manages changelogs/release notes from git history and Conventional Commits. Supports Keep a Changelog format, breaking change docs, migration guides, audience-specific notes.
Share bugs, ideas, or general feedback.
Automated changelog generation from conventional commits, integrated with the release workflow.
| Tool | Language | Approach |
|---|---|---|
git-cliff | Rust | Highly configurable, template-based, conventional commits |
cargo-release | Rust | Combines version bump + changelog + publish |
| GitHub "Generate release notes" | N/A | Built into gh release create --generate-notes |
cargo install git-cliff --locked
cliff.toml)[changelog]
header = "# Changelog\n\nAll notable changes to this project will be documented in this file.\n"
body = """
{% if version %}\
## [{{ version | trim_start_matches(pat="v") }}] - {{ timestamp | date(format="%Y-%m-%d") }}
{% else %}\
## [unreleased]
{% endif %}\
{% for group, commits in commits | group_by(attribute="group") %}
### {{ group | striptags | trim | upper_first }}
{% for commit in commits %}
- {% if commit.scope %}**{{ commit.scope }}:** {% endif %}\
{{ commit.message | upper_first }}\
{% endfor %}
{% endfor %}\n
"""
footer = ""
trim = true
[git]
conventional_commits = true
filter_unconventional = true
split_commits = false
commit_parsers = [
{ message = "^feat", group = "Features" },
{ message = "^fix", group = "Bug Fixes" },
{ message = "^doc", group = "Documentation" },
{ message = "^perf", group = "Performance" },
{ message = "^refactor", group = "Refactoring" },
{ message = "^style", group = "Styling" },
{ message = "^test", group = "Testing" },
{ message = "^chore\\(release\\)", skip = true },
{ message = "^chore", group = "Miscellaneous" },
{ message = "^ci", group = "CI/CD" },
]
filter_commits = false
tag_pattern = "v[0-9].*"
sort_commits = "oldest"
# Generate full changelog
git cliff -o CHANGELOG.md
# Generate changelog for latest tag only
git cliff --latest
# Generate since last tag (for release notes)
git cliff --unreleased --strip header
Add changelog generation to the release script before the version bump:
# In release.sh, after local checks and before branch creation:
echo "==> Generating changelog..."
if command -v git-cliff &>/dev/null; then
git cliff --tag "v$VERSION" -o CHANGELOG.md
git add CHANGELOG.md
fi
The publish workflow uses gh release create --generate-notes by default. To use git-cliff instead:
- name: Generate release notes
run: |
git cliff --latest --strip header > RELEASE_NOTES.md
- name: Create GitHub Release
env:
GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
run: |
gh release create "$TAG_NAME" \
--title "$TAG_NAME" \
--notes-file RELEASE_NOTES.md \
--verify-tag
For git-cliff to work well, use conventional commits:
feat: add support for workspace publishing
fix: correct SHA pin for codeql-action
docs: update migration guide for v0.19
feat(ci): add MSRV check job
fix(publish): handle workspace crate ordering
chore: bump cargo-audit to 0.22.1
| Prefix | Changelog Section | Semver Impact |
|---|---|---|
feat: | Features | Minor |
fix: | Bug Fixes | Patch |
feat!: or BREAKING CHANGE: | Breaking Changes | Major |
docs: | Documentation | None |
perf: | Performance | Patch |
refactor: | Refactoring | None |
test: | Testing | None |
ci: | CI/CD | None |
chore: | Miscellaneous | None |
--generate-notes vs git-cliff — GitHub's built-in notes are PR-based, git-cliff is commit-based; choose one approach--include-path to filter by directoryv1.0.0-rc.1 etc. but your tag_pattern must accommodate them