From docs-agent
Knowledge about Keep a Changelog standard for writing and maintaining changelogs
npx claudepluginhub wsagency/ws-claude-marketplace --plugin docs-agentThis skill uses the workspace's default tool permissions.
This skill provides comprehensive knowledge about the Keep a Changelog standard for writing human-readable changelogs.
Retrieves texts, DMs, one-time codes, and inspects threads in ECC workflows. Provides evidence of exact sources checked for verification before replies.
Delivers expertise for HS tariff classification, customs documentation, duty optimization, restricted party screening, and trade compliance across jurisdictions.
Process documents with Nutrient API: convert formats (PDF, DOCX, XLSX, images), OCR scans (100+ languages), extract text/tables, redact PII, sign, fill forms.
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.