Changelog writing
Skill Dragoon0x/everything-design-taste/skills/changelog-writing
A taste system for AI agents. 288 skills, 80 agents, 12 rules, and 8 hooks that turn generic AI output into work with genuine design quality. Anti-slop detection, typography craft, color systems, brand voice, product strategy, and 50+ specialized reviewers across UI, industry, platform, and content domains.
npx -y skills add Dragoon0x/everything-design-taste --skill changelog-writingAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 6 stars6 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Changelog and release notes writing patterns including versioning communication and user-facing updates.
SKILL.md
1.0 KB, as published. Nobody here has run it
Changelog Writing
Changelog Format
User-Facing
- Lead with benefit: "You can now export to PDF" not "Added PDF export module."
- Group: New, Improved, Fixed.
- Skip internal changes users don't care about.
- Link to docs for new features.
Developer-Facing
- Follow Keep a Changelog format.
- Group: Added, Changed, Deprecated, Removed, Fixed, Security.
- Reference issue/PR numbers.
- Highlight breaking changes prominently.
Semantic Versioning Communication
- Major (2.0): "Big update" — migration guide required.
- Minor (1.5): "New features" — backwards compatible.
- Patch (1.5.1): "Bug fixes" — no new features.
Anti-Patterns
- "Various bug fixes and performance improvements" — be specific.
- Technical jargon in user-facing notes.
- No date on entries.
- Changelog that's just git commit messages.