Changelog Automation
Writing & Docsby wshobson
3/3 audits passMIT
Automate changelog generation from commits, PRs, and releases following Keep a Changelog format. Use when setting up release workflows, generating release notes, or standardizing commit conventions.
Changelog Automation, published by wshobson in the agents repository under MIT, covers patterns for generating changelogs and release notes automatically. It explains the Keep a Changelog format (Added, Changed, Deprecated, Removed, Fixed, Security under an Unreleased section and versioned headings), Conventional Commits with scopes and breaking-change markers, and Semantic Versioning. A reference file shows six implementation methods: conventional-changelog with commitlint and husky, standard-version, semantic-release, a GitHub Actions release workflow, git-cliff and Python commitizen.
It also includes a release-notes template (summary, highlights, breaking changes, upgrade guide, known issues, dependency updates), commit message examples and a do/don't list: one logical change per commit, validate commits with commitlint in CI, never hand-edit generated changelogs and always mark breaking changes. Use it when setting up a release workflow or standardising commit conventions. It configures tooling and formats; it does not decide what your release contains.
This is mainly a skill for coding agents like Claude Code working in a repository; BusinessMCP can import it as a playbook but it has little to do with business data.
What you can do with it
- Set up commitlint and husky to enforce Conventional Commits
- Generate a Keep a Changelog file from commit history
- Automate versioning and releases with semantic-release
- Write release notes with highlights and an upgrade guide
Run it on your business data
Imported into BusinessMCP, Changelog Automation becomes a playbook your AI business analyst applies to your company knowledge and connected documents.
Use Changelog Automation in BusinessMCPInstall it in a coding agent
One command adds Changelog Automation to your project.
npx skills add https://github.com/wshobson/agents --skill changelog-automationHow we vetted it
- Source
- wshobson/agents at 4236bb9
- Licence
- MIT
- Security audits (skills.sh)
- Gen Agent Trust Hub: Pass · Socket: Pass · Snyk: Pass
- Bundled scripts
- None, instructions only
Checked 2026-09-25 against its skills.sh listing. How we vet skills
Related skills
All skillsChangelog Generator
Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes.
Writing Plans
Use when you have a spec or requirements for a multi-step task, before touching code
Test-Driven Development
Use when implementing any feature or bugfix, before writing implementation code
Frequently asked questions
How do I install Changelog Automation?
Run `npx skills add wshobson/agents --skill changelog-automation` to add it to a Claude Code or other skills-compatible agent. You can also import it from the BusinessMCP dashboard, where it becomes a playbook in your workspace.
Which tools does it cover?
conventional-changelog with commitlint and husky, standard-version, semantic-release, a GitHub Actions workflow, git-cliff and Python commitizen.
Should generated changelogs be edited by hand?
The skill's guidance is no: generate them from commits, validate commits in CI and mark breaking changes with ! or a BREAKING CHANGE footer.
Run Changelog Automation against your whole business
Free plan, no credit card.
Use Changelog Automation in BusinessMCP