Skip to main content
skill CX Codex

release-notes · garrytan — Claude Code skill: release notes

release-notes is a Claude Code skill that drafts Lantern release notes from merged PRs. It activates for requests about customer changelogs or what shipped.

MIT ★ 172 updated 2026-11-16

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add garrytan/g-harness-evals --skill release-notes -a claude-code
Open on GitHub

What release-notes does

The skill gathers merged PRs since the previous tag and keeps changes visible to customers. It filters out refactors, CI work, and dependency updates, then describes internal flags and identifiers in customer-facing terms.

Entries go into New, Improved, and Fixed sections, one line each, with no PR numbers. The draft is saved as release-notes/<version>.md; the skill then runs scripts/check.sh release-notes/<version>.md and fixes reported issues. It uses gh pr list to collect PRs, so the gh command is needed. The draft goes to #releases for Mira’s approval. The skill does not publish it.

What it helps with

  • draft customer release notes from merged PRs
  • filter out refactors and CI changes from a changelog
  • sort shipped changes into release note sections
  • run the release notes check script on a draft

Example prompts for the agent

  • Draft customer release notes for Lantern from merged PRs since the last tag.
  • Write a customer changelog for this release and save it to release-notes/<version>.md.
  • Summarize what shipped, then check the draft with scripts/check.sh.

How to install release-notes

1Skills CLI (Vercel)

npx skills add garrytan/g-harness-evals --skill release-notes -a claude-code

2Manually: put the files in place

~/.claude/skills/release-notes/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/release-notes/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about release-notes

How do I install release-notes in Claude Code?

Run npx skills add garrytan/g-harness-evals --skill release-notes -a claude-code. The skill file is installed at ~/.claude/skills/release-notes/SKILL.md.

What does release-notes do?

It turns merged Lantern PRs since the previous tag into customer-facing notes, sorts entries into New, Improved, and Fixed, then checks the draft.

What does release-notes need to run?

It uses gh pr list to fetch merged PRs, so the gh command is needed. Draft validation runs through scripts/check.sh.

Source text

SKILL.md · MIT
---
name: release-notes
description: Draft customer-facing release notes for a Lantern release from the merged PR list. Use when asked for release notes, a changelog for customers, or "what shipped".
---

# Release notes

1. Get the merged PRs since the last tag: `gh pr list --state merged --base main --search "merged:>=<last tag date>"`.
2. Keep only user-visible changes. Skip refactors, CI and dependency bumps.
3. Never mention internal feature-flag names (anything starting with `exp_`) or other internal identifiers; describe the feature in customer terms instead.
4. Group under **New**, **Improved** and **Fixed**. One line per change, in plain words a customer understands, no PR numbers.
5. Save the draft as `release-notes/<version>.md`.
6. Run `scripts/check.sh release-notes/<version>.md` from this folder and fix anything it reports.
7. Post the draft in #releases for Mira to approve. Never publish it yourself.

© garrytan · MIT · garrytan/g-harness-evals

Similar skills

All skills for Writing and docs →

release-notes by other authors comes first.

release-notes phuryn release-notes is a Claude Code skill that turns tickets and internal change logs into user-facing release notes. It runs for release write-ups and summaries of shipped updates. CX Codex +1 3,100installs release-notes anyproto Automates writing and updating release notes in whatsNew.ts with entries for features, improvements, and bug fixes. Pulls data from conversation context, git branches, or Linear issues. CX Codex +1 ★ 9,124repo stars release-notes kenryu42 release-notes updates the body of the latest GitHub Release using code diffs and merged pull requests via the gh command-line tool. CX Codex +1 ★ 2,088repo stars release-notes justxor Generates release notes and CHANGELOG entries between Git tags or from the latest tag to HEAD using Conventional Commits. CX Codex +1 ★ 353repo stars jackin-release-notes jackin-project jackin-release-notes collects PRs since the last tag, assigns Keep a Changelog categories, and updates the [Unreleased] section in CHANGELOG.md. CX Codex +1 469installs generate-release-notes teambit generate-release-notes pulls commits via GitHub CLI, discards CI noise, and formats structured release notes for Bit by change category. CX Codex +1 ★ 18,508repo stars update-release-notes tldraw update-release-notes — a skill that maintains the release notes file next.mdx in the tldraw repo: collects PRs since the last release and archives next.mdx to a versioned file when a new version ships. CX Codex +1 ★ 51,527repo stars draft-release-notes Cobus Greyling draft-release-notes generates categorized release notes drafts from repository scan data into clean Markdown. Keeps prompt injection safety checks active before you publish. CX Codex +1 ★ 11,819repo stars release-notes-showcase official Kayla Cinnamon release-notes-showcase — a GitHub Copilot plugin that drafts launch-ready release notes with contributor callouts. The output is meant for export, not just an internal changelog. ★ 41,430repo stars release-notes-composer qodex-ai release-notes-composer builds clear release notes and customer-facing changelogs directly from git commit history. CX Codex +1 134installs

From the same set4

Project sponsors

Companies that keep this analytics open