AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Release Notes

skill-phuryn-pm-skills-release-notes · by phuryn

Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.

No reviews yet
0 installs
28 views
0.0% view→install

Install

$ agentstack add skill-phuryn-pm-skills-release-notes

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No 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.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-phuryn-pm-skills-release-notes)

Reliability & compatibility

Security review passed
0 installs to date
no reviews yet
3mo ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

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 →
Are you the author of Release Notes? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Release Notes Generator

Transform technical tickets, PRDs, or internal changelogs into polished, user-facing release notes.

Context

You are writing release notes for $ARGUMENTS.

If the user provides files (JIRA exports, Linear tickets, PRDs, Git logs, or internal changelogs), read them first. If they mention a product URL, use web search to understand the product and audience.

Instructions

  1. Gather raw material: Read all provided tickets, changelogs, or descriptions. Extract:
  • What changed (feature, improvement, or fix)
  • Who it affects (which user segment)
  • Why it matters (the user benefit)
  1. Categorize changes:
  • New Features: Entirely new capabilities
  • Improvements: Enhancements to existing features
  • Bug Fixes: Issues resolved
  • Breaking Changes: Anything that requires user action (migrations, API changes)
  • Deprecations: Features being sunset
  1. Write each entry following these principles:
  • Lead with the user benefit, not the technical change
  • Use plain language — avoid jargon, internal codenames, or ticket numbers
  • Keep each entry to 1-3 sentences
  • Include visuals or screenshots if the user provides them

Example transformations:

  • Technical: "Implemented Redis caching layer for dashboard API endpoints"
  • User-facing: "Dashboards now load up to 3× faster, so you spend less time waiting and more time analyzing."
  • Technical: "Fixed race condition in concurrent checkout flow"
  • User-facing: "Fixed an issue where some orders could fail during high-traffic periods."
  1. Structure the release notes:

``` # [Product Name] — [Version / Date]

## New Features

  • [Feature name]: [1-2 sentence description of what it does and why it matters]

## Improvements

  • [Area]: [What got better and how it helps]

## Bug Fixes

  • Fixed [issue description in user terms]

## Breaking Changes (if any)

  • Action required: [What users need to do]

```

  1. Adjust tone to match the product's voice — professional for B2B, friendly for consumer, developer-focused for APIs.

Save as a markdown document. If the user wants HTML or another format, convert accordingly.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

  • Author: phuryn
  • Source: phuryn/pm-skills
  • License: MIT
  • Homepage: https://www.productcompass.pm/p/pm-skills-2-red-team-ship

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Versions

  • v0.1.0 Imported from the upstream source.