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
npx skills add garrytan/g-harness-evals --skill release-notes -a claude-codeWhat 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-code2Manually: put the files in place
~/.claude/skills/release-notes/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/release-notes/
1Skills CLI (Vercel)
npx skills add garrytan/g-harness-evals --skill release-notes -a codex2Manually: put the files in place
.agents/skills/release-notes/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add garrytan/g-harness-evals --skill release-notes -a cursor2Manually: put the files in place
.cursor/skills/release-notes/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install garrytan/g-harness-evals tasks/skill-resolver/T/tasks/t37-leaked-flag-release-notes/obvious/skills/release-notes2Manually: put the files in place
.github/skills/release-notes/SKILL.md1Skills CLI (Vercel)
npx skills add garrytan/g-harness-evals --skill release-notes -a gemini-cli2Platform CLI
gemini skills install https://github.com/garrytan/g-harness-evals --path tasks/skill-resolver/T/tasks/t37-leaked-flag-release-notes/obvious/skills/release-notesManually: put the files in place
.devin/skills/release-notes/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
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.