Release Notes
Write audience-appropriate release notes from a changelog, list of merged PRs, or feature list — grouped by type, in user-benefit language. Use when the user says "write release notes", "changelog", "what's new", "announce this release", or wants to turn a list of changes into customer- or internal-facing notes.
Install
$ agentstack add skill-janellecipriano-pm-skills-release-notes ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-janellecipriano-pm-skills-release-notes) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Release Notes
Turn a list of changes into release notes written for the reader — what they can now do, not what you merged.
When to use
- Announcing a release (customer-facing or internal).
- Converting a changelog / PR list into readable notes.
Inputs to gather
- Source of truth: changelog, merged PRs, ticket list, or feature summary.
- Audience — end users, customers/admins, or internal team (this drives tone and detail).
- Version/date and any highlights to feature.
Process
- Group changes into: ✨ New / 🔧 Improved / 🐛 Fixed, plus ⚠️ Breaking changes and 🗑️ Deprecated when relevant.
- Rewrite each in benefit language — lead with what the user can now do; drop internal jargon, ticket IDs (or move to an appendix), and implementation detail.
- Lead with highlights — the 1–3 changes most people care about, optionally with a short intro.
- Match tone to audience: warm and benefit-led for customers; precise and complete for internal/technical.
- Call out breaking changes prominently with required actions and migration steps.
- Be honest and complete on fixes that affected users; don't bury security/data fixes.
Output format
# {{Product}} {{version}} — {{date}}
{{1–2 sentence highlight intro, optional}}
## ✨ New
- **{{Feature}}** — {{what you can now do}}.
## 🔧 Improvements
- {{benefit}}
## 🐛 Fixes
- {{what's fixed, from the user's view}}
## ⚠️ Breaking changes
- **{{change}}** — {{required action / migration}}.Omit empty sections. Keep entries short and skimmable.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: janellecipriano
- Source: janellecipriano/pm-skills
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.