Skip to content
SkillModel-led519 tokens in use

release-notes

Turn tickets, PRDs and changelogs into user-facing release notes grouped by new features, improvements, fixes and breaking changes.

28,201 stars on the repository MIT Licensephuryn/pm-skills · pm-execution/skills/release-notes
claude plugin install pm-execution@pm-skills
View source

Install command as written in the repository's README

Skill label

measured from its files

What installing release-notes costs

56tokens idle
519tokens in use

Idle is what sits in context while the skill is installed. In use is its instructions, loaded when it runs. Counts are approximate, made offline with cl100k_base.

Model dependence Model-led

Script-ledMixedModel-led

Mostly instructions, so how well it works depends on the model that follows them.

This describes the skill's structure, how much of it is scripts. It does not say how well it works.

Touches

Nothing detected: no shell, network, file writes, git or credentials in its files.

Declared tags come from the skill's frontmatter; detected ones from its scripts, its code blocks and the commands it names in inline code. This is detected, not audited.

How it scores

Quality

How well the skill is written, counted from its own files: its frontmatter, its steps, examples, stated output and constraints, its size and whether every file it ships is one it names.How we score it →
Good
  • Frontmatter12/15
  • Structure23/25
  • Examples9/15
  • Output7/15
  • Size15/15
  • Resources10/15

Security

Starts at 100 and loses points for each thing in the skill's files that a reader should look at first.How we score it →
Excellent

No findings.

Repository health

Pre-computed score based on development activity, maintenance, community, maturity, and trend momentum.How we score it →
Good
  • Development activity80
  • Maintenance76
  • Community60
  • Maturity32
  • Momentum40

release-notes converts technical material such as JIRA exports, Linear tickets, PRDs, git logs and internal changelogs into release notes for users. Each entry leads with the user benefit, avoids jargon and codenames, and stays within one to three sentences.

Changes are sorted into new features, improvements, bug fixes, breaking changes and deprecations, and the tone is matched to the product: professional for B2B, friendly for consumer, developer-focused for APIs.

What You Get

  • Release notes with a title carrying the product name and version or date
  • New Features, Improvements and Bug Fixes sections
  • A Breaking Changes section with the action users must take, when there is one
  • Entries free of ticket numbers and internal codenames
  • A markdown file, or another format on request

Common Use Cases

  • Writing notes for a sprint release from a ticket export
  • Announcing an API change with a clear action required
  • Summarizing a git log for customers

What Makes It Unique

It rewrites by example: a technical change is shown beside its user-facing form, so entries describe the benefit before the mechanism. It separates breaking changes and deprecations into their own sections so required actions are not buried.

Under The Hood

The skill is one SKILL.md of instructions with no scripts. The agent reads the ticket, PRD or changelog files you provide and may use web search on a product URL you mention to learn the product and audience. It saves the notes as a markdown file, and converts to HTML or another format on request.

Join founders building with open source

Opinionated takes, migration guides, cost-saving tips, and insights from the open source ecosystem.

Subscribe on SubstackJoin 750+ subscribers