changelog-rewriter

To rewrite changelog entries with a narrative tone, apply this skill to your local CHANGELOG.md. It converts dry release notes into concise, witty summaries while preserving your repository's existing structure and style guidelines.

Yes, you can automate release notes generation for multi-change Markdown releases. The skill applies a consistent cheeky voice across both single-patch updates and multi-change releases, integrating seamlessly into automated pipelines without requiring external services.

The best way to make dry changelog updates engaging for public documentation is using a narrative rewriting tool. This skill transforms standard project updates into readable, concise summaries that explain what changed and why.

No, changelog rewriting does not require external services or API dependencies. The skill operates entirely on the local CHANGELOG.md, following your repository's existing conventions and structure for both automated pipelines and manual edits.

No, rewriting changelogs will not alter your existing Markdown formatting. The skill explicitly preserves project conventions and repository structure, applying tone consistency only to the text content of your release notes.