release-notes-writer SKILL.md skillA
release-notes-writer from qa-aman/claude-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add qa-aman/claude-skills/release-notes-writer@git:20260323.7a669c3Pins git:20260323.7a669c3 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- qa-aman/claude-skills
- Path
skills/by-role/pm/release-notes-writer/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260323.7a669c3, committed Mar 23, 2026
- Size
- 3,608 bytes
- Repository stars
- 25
- License
- MIT
Generate ship-ready release notes from specs and tickets. Use this skill when: - A release is being prepared and you need user-facing release notes - You need internal (engineering) release notes for a deployment - You want to generate release notes from completed specs or tickets.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Release Notes Writer
Generate structured release notes for each release cycle. Produces both **user-facing** (what changed and why it matters) and **internal** (technical changes, migration steps) release notes.
## Workflow
1. **Identify release scope** — List the features/fixes included
2. **Read source specs** — Read relevant spec files
3. **Read tickets** — If available, read completed tickets for the release
4. **Categorize changes** — Group into: New Features, Enhancements, Bug Fixes, Known Issues
5. **Write user-facing notes** — What changed, why it matters, in plain language
6. **Write internal notes** — Technical changes, migration steps, config changes
7. **Output** — Write to file
## User-Facing Release Notes
```markdown
# [Product Name] — Release Notes {version}
**Release Date:** {DD-MM-YYYY}
**Environment:** {Production / Staging / UAT}
## What's New
### {Feature Name}
{1-2 sentence description of what the feature does and why it matters.}
**Highlights:**
- {Key capability 1}
- {Key capability 2}
## Enhancements
### {Enhancement Name}
{What improved and why it's better now.}
| Before | After |
|--------|-------|
| {Old behavior} | {New behavior} |
…Read the whole file at its exact version.
How to install
mdr add qa-aman/claude-skills/release-notes-writer@sha256:fe9224741a82d63bThe line at the top of this page pins the label git:20260323.7a669c3, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_vfn4qsny2zpiuho3)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Mar 23, 2026.
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (3608 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
qa-aman/claude-skills · 25 stars · license MIT · pushed 2026-10-19 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_vfn4qsny2zpiuho3 GET https://markdownregistry.com/api/v1/resolve?ref=qa-aman/claude-skills/release-notes-writer GET https://markdownregistry.com/api/v1/blob/fe9224741a82d63b1fabb07ab5ab1eebd85fc3f43e2d1cc9466818d73102d87b
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.
More from qa-aman/claude-skills
Every file in qa-aman/claude-skills