product-changelog

What This Skill Does

The product-changelog skill is a specialized communication and documentation agent designed to help teams craft high-impact release notes and product updates. Unlike generic writing assistants, this skill enforces a strict pedagogical framework that prioritizes user-facing value over internal engineering jargon. It handles the nuances of semantic versioning (SemVer), categorizes changes according to professional standards, and integrates directly with visual generation tools via inference.sh to create marketing-ready assets. By automating the transformation of technical pull requests into engaging update logs, this skill ensures your users actually look forward to reading your release notes.

Installation

To integrate this skill into your workflow, use the ClawHub CLI command:

clawhub install openclaw/skills/skills/okaris/product-changelog

Ensure you have the inference.sh CLI installed to leverage the visual generation capabilities, as the skill uses it to generate mockups and feature banners based on your changelog content.

Use Cases

• Feature Announcements: Launching new product capabilities with clear, benefit-driven messaging.
• Weekly Update Logs: Compiling bug fixes and minor improvements into a digestible format for stakeholders.
• Version Release Documentation: Generating professional release notes that align with SemVer standards.
• Internal Syncs: Translating complex Git commit logs into non-technical language for customer success and marketing teams.

Example Prompts

1. "Draft a release note for our new dark mode feature. It falls under the 'Improved' category and should emphasize reduced eye strain and better battery life."
2. "Convert this list of bug fixes into a polished changelog entry: fixed login loop, resolved API 500 errors on dashboard, and patched the memory leak in the export module."
3. "Create a professional version 2.4.0 announcement. We added bulk CSV uploads and removed the deprecated XML legacy importer. Keep it punchy and professional."

Tips & Limitations

• Always Focus on Value: The skill will penalize internal "how-it-works" language. Always frame entries around what the user can now do.
• Category Discipline: Avoid the generic "Updated" label. If you are struggling to categorize an entry, ask yourself: did this add a capability (New), make an existing one better (Improved), or fix a broken behavior (Fixed)?
• Visuals are Optional: While the skill is capable of generating visuals via falai/flux-dev-lora, ensure the text stands on its own in case of API latency or image generation timeouts.
• Versioning: Always verify your SemVer logic before publishing. The skill will provide suggestions, but final authority on breaking changes (MAJOR) should remain with your engineering lead.