How do I install the Draft Release Notes skill?

Run npx skillmds@latest add gabrielmoreira/draft-release-notes in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Draft Release Notes safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only, makes network calls. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Draft Release Notes?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Draft Release Notes free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Draft Release Notes?

gabrielmoreira (@gabrielmoreira) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Draft Release Notes by gabrielmoreira

Name: Draft Release Notes
Rating: 4.2 (5 reviews)
Author: gabrielmoreira

Draft Release Notes

Takes a structured list of changes from changelog-scan and produces a clean, categorized, user-facing release notes draft. Follows project voice and conventions. Never publishes — only proposes a draft file or section.

gabrielmoreira Updated Sep 9, 2026 17 repo stars

File contents

Draft Release Notes Skill

Inputs

Structured output from changelog-scan (the list of items + summary)
Previous release version (from state)
Target next version (or "unreleased" / "next")
Optional: short "Release voice" guidance from AGENTS.md or a project skill (tone, what to highlight, what to omit)

Output

Write a ready-to-review draft to RELEASE_NOTES_DRAFT.md (or print it clearly so the loop can save it).

Use this structure (adapt section names to what actually exists; omit empty sections):

# Release Notes — vX.Y.Z (unreleased)

## Breaking Changes
- ...

## Features
- ...

## Bug Fixes
- ...

## Performance
- ...

## Security
- ...

## Documentation & Examples
- ...

## Internal / Maintenance (usually omitted from public notes)
- ...

**Thanks** to @contributor1, @contributor2 for contributions to this release.

**Full changelog**: https://github.com/ORG/REPO/compare/vPREV...HEAD

Rules

Be concise and scannable. One line per item when possible, with link to PR.
Use the actual title / one-sentence summary from the scan. Do not embellish or add marketing fluff unless the project voice explicitly wants it.
Always call out breaking changes and security items at the top.
If a change has a user upgrade step that is obvious from the PR, include a one-sentence "Upgrade note".
Never claim a change was made if it was not in the scanned input.
At the very end of the draft, include a short "Draft generated by loop — please review for accuracy and tone before publishing."

When to Escalate Instead of Drafting

More than ~40 items in one window → suggest splitting the release or human curation.
Any breaking or security item → include prominent callout and recommend human wordsmithing.
The scan summary says "human review needed first".

After writing the draft, the loop should update state with the draft location and "pending human review".

---name: draft-release-notesdescription: Takes a structured list of changes from changelog-scan and produces a clean, categorized, user-facing release notes draft. Follows project voice and conventions. Never publishes — only proposes a draft file or section.--- # Draft Release Notes Skill ## Inputs - Structured output from `changelog-scan` (the list of items + summary) - Previous release version (from state) - Target next version (or "unreleased" / "next") - Optional: short "Release voice" guidance from AGENTS.md or a project skill (tone, what to highlight, what to omit) ## Output Write a ready-to-review draft to `RELEASE_NOTES_DRAFT.md` (or print it clearly so the loop can save it). Use this structure (adapt section names to what actually exists; omit empty sections): ```markdown # Release Notes — vX.Y.Z (unreleased) ## Breaking Changes - ... ## Features - ... ## Bug Fixes - ... ## Performance - ... ## Security - ... ## Documentation & Examples - ... ## Internal / Maintenance (usually omitted from public notes) - ... **Thanks** to @contributor1, @contributor2 for contributions to this release. **Full changelog**: https://github.com/ORG/REPO/compare/vPREV...HEAD ``` ## Rules - Be concise and scannable. One line per item when possible, with link to PR. - Use the actual title / one-sentence summary from the scan. Do not embellish or add marketing fluff unless the project voice explicitly wants it. - Always call out breaking changes and security items at the top. - If a change has a user upgrade step that is obvious from the PR, include a one-sentence "Upgrade note". - Never claim a change was made if it was not in the scanned input. - At the very end of the draft, include a short "Draft generated by loop — please review for accuracy and tone before publishing." ## When to Escalate Instead of Drafting - More than ~40 items in one window → suggest splitting the release or human curation. - Any breaking or security item → include prominent callout and recommend human wordsmithing. - The scan summary says "human review needed first". After writing the draft, the loop should update state with the draft location and "pending human review".

Frequently asked questions