Agent skill · marketing growth · aiskillstore
product-changelog
Product changelog and release notes that users actually read. Covers categorization, user-facing language, visuals, and distribution. Use for: release notes, changelogs, product updates, feature announcements, versioning. Triggers: changelog, release notes, product update, version notes, what's new, feature announcement, product changelog, update log, release announcement, version release, product release, ship notes
Why this skill is useful
Provides specific guidelines and templates for creating user-friendly changelogs and release notes that enhance communication with users.
What it needs
Requires inference.sh installed locally. About 5k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.
What this skill does
Product Changelog Write changelogs and release notes that users read and care about via inference.sh CLI. Quick Start Install note: The install script only detects your OS/architecture, downloads the matching binary from dist.inference.sh, and verifies its SHA-256 checksum. No elevated permissions or background processes. Manual install & verification available. Entry Format The Anatomy of a Good Entry Structure: Category label -> User-facing title -> What you can do now -> How -> What changed -> Visual User-Facing Language Rules: Write what the user can DO, not what you BUILT Start with "You can now..." / "Reports now..." / "Fixed an issue where..." Include the benefit, not just the mechanism Use present tense Categories Standard Categories Category Color Icon Use For ---------- ------- ------ --------- New Green ✨ or 🆕 Entirely new features or capabilities Improved Blue ⚡ or 🔧 Enhancements to existing features Fixed Yellow/Orange 🐛 or 🔨 Bug fixes Removed Red 🗑️ or ⚠️ Deprecated or removed features Security Purple 🔒 Security patches Categorization Rules New = something users couldn't do before at all Improved = something users could do, now it's better/faster/easier Fixed = something that was broken, now works correctly Don't use "Updated" — it's meaningless. Was it improved or fixed? Version Numbering Semantic Versioning (SemVer) Component Increment When Example ----------- --------------- --------- MAJOR Breaking changes, major redesign 2.0.0 -> 3.0.0 MINOR New features, backward-compatible 3.1.0 -> 3.2.0 PATCH Bug fixes, small improvements 3.2.0 -> 3.2.1 Date-Based Versioning Best for SaaS products with continuous deployment. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/product-changelog