changelog-curator

What This Skill Does

The changelog-curator is a specialized AI agent skill designed to bridge the gap between raw development metadata and polished, user-facing documentation. It excels at processing technical noise—such as Git commit messages, Pull Request (PR) summaries, and engineering release notes—and transforming them into structured, readable changelogs. By categorizing changes based on user impact versus internal technical debt, this skill ensures that stakeholders stay informed about what matters to them while keeping internal engineering details appropriately separated. It follows a strict structured output format to ensure consistency across your project's documentation lifecycle.

Installation

To integrate this skill into your OpenClaw environment, execute the following command in your terminal: clawhub install openclaw/skills/skills/52yuanchangxing/changelog-curator Once installed, ensure your project directory has access to the standard {baseDir}/resources/ folder to utilize the provided templates and specifications.

Use Cases

• Automated Release Notes: Generate high-quality release summaries directly from PR merge histories.
• Stakeholder Communication: Differentiate between new user features and backend refactoring to prevent confusion in public-facing docs.
• Technical Documentation Maintenance: Keep your project's CHANGELOG.md synchronized with actual development activity without manual formatting efforts.
• Audit Preparation: Create structured lists of changes for compliance reviews by separating user-impactful changes from internal maintenance.

Example Prompts

1. "Here are the last 15 PR titles from our repo: [list of PRs]. Please draft a user-facing changelog for v2.4.0, grouping items into user features and performance improvements."
2. "I have a rough list of changes for our latest release. Can you format this into the standard template, identify any missing information that needs confirmation, and highlight potential breaking changes?"
3. "Summarize these commit messages into a concise 'Internal Improvements' section, ensuring no sensitive configuration details are exposed in the final output."

Tips & Limitations

• Manual Review is Mandatory: While the curator is excellent at categorization, always perform a final human review for sensitive disclosures, marketing tone, and technical accuracy.
• Data Privacy: Avoid inputting proprietary secrets or sensitive environment variables in your commit logs that you would not want appearing in your public-facing documentation.
• Strict Boundaries: This skill is strictly for curating text. It does not possess the authority to trigger deployments, update system configurations, or bypass compliance workflows. Always use the 'Draft' output mode for initial verification.