product-changelog

Writes user-facing changelogs and release notes with categorization, versioning, and visuals.

Updated Jul 28, 2026
One-click install
npx skills add https://github.com/Aadi-110i/PEP-PROJECT --skill product-changelog-aadi-110i
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: product-changelog
Source: https://github.com/Aadi-110i/PEP-PROJECT/tree/main/skills/product-changelog
Command: npx skills add https://github.com/Aadi-110i/PEP-PROJECT --skill product-changelog-aadi-110i

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams often publish changelogs written in internal developer language that users ignore or misunderstand. This Skill converts raw changes into clear, user-facing release notes with proper categorization, versioning, visuals, and distribution guidance. ## Core Features & Use Cases - User-Facing Entry Writing: Transforms internal commit messages into benefit-driven entries using the "You can now..." format with category labels (New, Improved, Fixed, Removed, Security). - Versioning & Structure Guidance: Applies Semantic Versioning or date-based versioning and provides a complete changelog page structure with dated, grouped entries. - Visual Generation: Generates feature screenshots, before/after comparisons, annotated callouts, and announcement banners via the inference.sh belt CLI. - Use Case: After shipping a bulk export feature, use this Skill to write the changelog entry, generate a product screenshot, and produce a social media announcement snippet. ## Quick Start Ask the assistant to write a user-facing changelog entry for your latest feature release, including category, benefit-focused description, and a generated announcement visual.

Frequently Asked Questions about product-changelog

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write release notes that users actually read?

Write what users can do, not what you built. Start entries with "You can now..." or "Fixed an issue where...", group changes under New, Improved, and Fixed categories, and add screenshots for major features.

How to categorize changelog entries correctly?

Use New for capabilities users never had, Improved for enhancements to existing features, Fixed for broken behavior now corrected, Removed for deprecations, and Security for patches. Avoid vague labels like "Updated".

What is the difference between Semantic Versioning and date-based versioning?

Semantic Versioning uses MAJOR.MINOR.PATCH where majors signal breaking changes, minors add features, and patches fix bugs. Date-based versioning like 2026.02.08 suits SaaS products with continuous deployment.

How should breaking changes be announced in a changelog?

Breaking changes need a prominent warning with what changed, step-by-step migration instructions, a timeline with deprecation dates, and a support contact. Never bury them among routine entries.

Can I generate changelog visuals without design tools?

Yes, the inference.sh belt CLI generates feature screenshots, before/after comparisons, annotated callouts, and announcement banners using apps like falai/flux-dev-lora and bytedance/seededit-3-0-i2i.