Product Changelog
Product changelog and release notes that users actually read.
Install
npx skills add inference-sh/skills --skill product-changelog -g -a claude-code -y- Repository
- inference-sh/skills795
- Category
- Git and review
- Updated
- 20d ago
- License
- See repository
- Context cost
- Mediumabout 1,978 tokens
- Runs scripts
- No, instructions only
What it does
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
Install the belt CLI skill:
npx skills add belt-sh/cli
Product Changelog
Write changelogs and release notes that users read and care about via inference.sh CLI.
Quick Start
Requires inference.sh CLI (
belt). Install instructions
belt login
# Generate a feature announcement visual
belt app run falai/flux-dev-lora --input '{
"prompt": "clean product UI screenshot mockup, modern dashboard interface showing a new analytics chart feature, light mode, minimal design, professional SaaS product",
"width": 1248,
"height": 832
}'
Entry Format
The Anatomy of a Good Entry
### New: Bulk Export for Reports š
You can now export up to 10,000 rows at once from any report view.
Select your rows, click Export, and choose CSV or Excel format.
Previously limited to 500 rows per export.
Structure: Category label -> User-facing title -> What you can do now -> How -> What changed -> Visual
User-Facing Language
ā Internal language:
"Implemented batch processing queue for the export service"
"Refactored the ReportExporter class to support pagination"
"Fixed bug in CSV serialization (PR #4521)"
ā
User-facing language:
"You can now export up to 10,000 rows at once from any report"
"Reports now load 3x faster when filtering large datasets"
"Fixed an issue where exported CSV files had missing columns"
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
