What is release-notes?

A release-notes writing workflow that turns technical tickets or a product requirements document into updates written around user benefits. Release notes explain what changed in a new software version.

Use it to prepare updates for an in-app message, email, marketing material, or blog after features or fixes are released.

It makes technical work understandable to customers, executives, and other non-technical readers instead of listing implementation details.

release-notes — Command for Claude Code by lucasgaravelli

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Clone the repo

git clone --depth 1 https://github.com/lucasgaravelli/pm-skills-claude-code

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/commands/lucasgaravelli/pm-skills-claude-code/release-notes/github.svg)](https://agentmods.dev/commands/lucasgaravelli/pm-skills-claude-code/release-notes)

Your own site

<a href="https://agentmods.dev/commands/lucasgaravelli/pm-skills-claude-code/release-notes"><img src="https://agentmods.dev/badge/commands/lucasgaravelli/pm-skills-claude-code/release-notes/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/commands/lucasgaravelli/pm-skills-claude-code/release-notes"><img src="https://agentmods.dev/badge/commands/lucasgaravelli/pm-skills-claude-code/release-notes.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 1,871 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin 100% copy Near-identical to another mod in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00000	$0.01871
Opus 5.5	$0.00000	$0.00748
Sonnet 5.5	$0.00000	$0.00374
Haiku 4.5	$0.00000	$0.00187

Measured 1mo ago against content hash 232b478447f3, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

release-notes scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

Origin

This is a copy

100% identical to release-notes — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.claude/commands/release-notes.md · 285 lines

How it starts

The opening of the file, as written. The whole thing — 285 lines — stays where its author put it; the contents beside it link to each section on GitHub.

/release-notes

O que essa skill faz

Converte tickets técnicos ou PRD em release notes orientadas a benefício, focadas no que usuário ganha (não o que foi feito).

Saída: Release notes em formato pronto para marketing, in-app, ou blog.

Quando usar

Feature saiu do dev e precisa comunicar para clientes
Sprint terminou, need summary para update executivo
Launch de novo produto/feature grande

Input esperado

Mínimo:

Tickets/features que shiparam: Nomes ou descrições
Contexto de negócio: O que resolve para usuário?
Público-alvo: Todos os users ou segmento específico?

Opcional:

Design mockups (para screenshot em blog)
Metrics esperadas
Customer quotes

Processo

Extração de benefício — Por cada feature, qual problema resolve?
Linguagem de usuário — Nada de "we optimized API", falar em valor
Priorização — Features mais impactantes primeiro
Call to action — Se aplicável
Formatting — Adequado para canal (in-app, email, blog)

Output

# Release Notes — [Data/Versão]

## Headline
[1 frase que resume o update — o que mais importa]

---

## What's new

### [Feature 1 Name]
**What's changed**: [Descrição clara do que é novo]

**Why it matters**: [Qual problema resolve ou valor cria]

**What you can do now**: [Como usuário usa — 1-2 sentença]

---

### [Feature 2 Name]
**What's changed**: [...]

**Why it matters**: [...]

**What you can do now**: [...]

---

## Bug fixes
- [Bug 1]: Fixed [o que estava errado]
- [Bug 2]: [...]

---

## Performance
- [Performance improvement]: [Métrica — ex: "Deal loading 50% faster"]

---

## CTA
[Optional] "Try it now → [link]" ou "Learn more → [docs]"

---

## FAQ

**Q: [Common question]**
A: [Answer]

---

## Coming soon
- [Feature que está em progress — set expectations]

---

## Feedback
Have a suggestion? Email us at product@[company].com

Exemplo

Input:

/release-notes
Features que shiparam:
- Guided onboarding tutorial
- Email sync com Salesforce
- Deal health score (beta)

Público: Todos os users
Contexto: Q1 launch, maior update de produto

Read the full file on GitHub · 285 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

1mo ago First seen · 285 lines · 0 tokens per session scan A 232b478447f3

Subscribe to this mod's changes

release-notes is a command published in the GitHub repository lucasgaravelli/pm-skills-claude-code (20 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,871 tokens. A static security scan graded it A with 0 findings. It is 100% identical to release-notes, differing in 0 lines, and is treated as a copy.

Git and workflow Releases Writing and docs

release-notes