asapp-improve-changelog

Clean up GitHub release notes by using a Skill that tightens wording, removes low-value entries, and merges duplicates without changing meaning. It processes the changelog for a specific tag and requires explicit confirmation before editing the release.

Yes, GitHub CLI access is required. The Skill depends on the GitHub CLI to discover release tags, retrieve existing release notes, and apply the polished editorial changes directly to the repository after user confirmation.

Polishing GitHub changelog entries preserves all commit links and breaking changes. The editorial cleanup focuses on normalizing tone and removing duplicate updates without dropping critical safety and versioning information from the release notes.

To improve release notes for a specific version, instruct the Skill to target the specific release tag. It retrieves the notes for that version, proposes editorial cleanups to normalize tone and remove noise, and waits for your confirmation before updating.

Yes, you can rewrite terse notes into clearer release language. The Skill merges duplicate updates and rewrites awkward phrasing into polished changelog entries, turning a noisy release draft into a clean, ready-to-publish release note.

The best way to remove noise from GitHub release drafts is to apply an editorial cleanup pass that merges duplicate updates and filters low-value entries. The Skill normalizes tone while preserving commit links and breaking changes, requiring confirmation before publishing.