product-changelog

Write changelogs and release notes that users read and care about via inference.sh CLI. Requires inference.sh CLI ( infsh ). Get installation instructions: npx skills add inference-sh/skills@agent-tools Structure: Category label -> User-facing title -> What you can do now -> How -> What changed -> Visual Rules: Best for SaaS products with continuous deployment. Breaking changes need special treatment: Browse all apps: infsh app list - 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 - 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? - Group related changes together - Lead with the biggest/most requested change - Link to documentation for complex features - Include who requested it ("By popular request:") - Show migration paths for breaking changes - Date every entry - Don't say "various bug fixes" — list specific fixes or skip them - Don't include internal references (PR numbers, ticket IDs, branch names) - Don't use "Updated [feature]" without saying how - Don't list changes nobody cares about (dependency bumps, internal refactors) - Don't...