Draft GitHub release notes with curated sections and strict structure.
npx skills add https://github.com/CertaMesh/gaze --skill release-notes-certamesh
Please help me install this Agent Skill. Skill: release-notes Source: https://github.com/CertaMesh/gaze/tree/main/.claude/skills/release-notes Command: npx skills add https://github.com/CertaMesh/gaze --skill release-notes-certamesh
Draft GitHub release notes with a curated narrative and strict structure, so teams communicate changes clearly and maintain a consistent voice across releases.
Draft the release body for vX.Y.Z following the curated structure and narrative voice.
High-intent search queries and answers about installing and using this skill.
To draft GitHub release notes with a consistent narrative voice, use a structured template that enforces exact section ordering, required terminology, and inline PR anchor references. This ensures every software release maintains a curated, unified communication style across repositories.
A structured software change log should include an Opening paragraph, TL;DR, Highlights, Known limitations, Adopter notes, Download, and Full CHANGELOG sections. Enforcing this exact section ordering ensures adopters clearly understand release scope and impact.
To generate release notes aligned with the Keep-a-Changelog format, follow a strict template that maps curated narrative sections to versioned links. This maintains structural consistency while guiding authors through gating and QA checks for accurate impact communication.
Yes, you can enforce required terminology and PR anchor references in GitHub release notes by using a strict drafting structure. This guarantees that inline references and specific vocabulary remain consistent across all software releases.
The best way to communicate known limitations to software adopters is to include a dedicated Known limitations and Adopter notes section within your release notes. This structured approach accurately conveys release scope and impact alongside the main highlights.
Release notes formatting breaks across repositories when lacking a strict structure enforcing exact section ordering and required terminology. Applying a standardized template with a curated narrative voice ensures consistent formatting and reliable versioned CHANGELOG links.
pacaplanCreate release pull requests with semantic version bumps and changelog entries.
shellicarCreate GitHub releases from version tags to trigger npm-publish workflows.
liujiayi3703Monitor pull request status and manage review threads via GitHub CLI.
o9nnCompile git commits, PR summaries, and change notes into a standardized changelog document.
