From docs-agent
Knowledge about Keep a Changelog standard for writing and maintaining changelogs
How this skill is triggered — by the user, by Claude, or both
Slash command
/docs-agent:keep-a-changelogThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
This skill provides comprehensive knowledge about the Keep a Changelog standard for writing human-readable changelogs.
This skill provides comprehensive knowledge about the Keep a Changelog standard for writing human-readable changelogs.
Use these sections in this order:
Only include sections that have entries. Empty sections should be omitted.
Follow Semantic Versioning (SemVer):
Always maintain an [Unreleased] section at the top:
These are complementary but different artifacts:
| Changelog (CHANGELOG.md) | Release Notes |
|---|---|
| Developer-facing, technical | User-facing, benefit-driven |
| Comprehensive — every fix | Curated — only what users care about |
| In the repository | Published on website/blog/in-app |
| Follows Keep a Changelog format | Follows Linear's changelog style |
When combined with Conventional Commits and release-please:
feat:, fix:, etc.This keeps the changelog always up-to-date with zero manual effort.
See references/changelog-format.md for the detailed format specification.
See examples/changelog-template.md for a ready-to-use template.
npx claudepluginhub wsagency/ws-claude-marketplace --plugin docs-agentAutomates 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.
Creates and maintains human-readable changelogs following Keep a Changelog standards. Useful for documenting releases, version history, and transparent communication.
Automates changelog generation from commits, PRs, and releases following Keep a Changelog format. Use for release workflows, generating release notes, or standardizing commit conventions.