update-release-notes — Claude Code skill: what it does, how to install
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.
no license ★ 51,527 updated 2026-10-24
npx skills add tldraw/tldraw --skill update-release-notes -a claude-codeWhat update-release-notes does
The skill works with a local clone of tldraw/tldraw and updates apps/docs/content/releases/next.mdx. It determines where to pull changes from: main (three weeks of development) or production (freeze week before release). In the first case, it gathers PRs via git cherry from the last tag; in the second, it compares patches between production and the previous release branch to include only hotfixes that made it to production.
Internally, bash scripts call git and gh to retrieve PR lists, details, and branch status. The skill distinguishes commits without PR numbers (hotfixes) and searches for them via sdk-hotfix-please labels. Without a clone of the repo in /tmp/tldraw, the skill will not run.
When a new version is published, the skill copies next.mdx to a file named vX.Y.0.mdx, updates the releases index in releases.mdx, and clears next.mdx for the next cycle. It removes PRs from the notes that were accumulated from main but did not reach production — those are deferred to the next release.
What it helps with
- update next.mdx with merged PRs since last release
- archive next.mdx to a versioned file after a release
- filter out PRs that did not reach production after freeze
- find hotfixes without PR numbers via gh and labels
- sync release notes between main and production branches
Example prompts for the agent
- Check the release cycle status for tldraw and tell me which branch to gather changes from
- Collect new PRs into next.mdx for tldraw since the last tag
- Archive next.mdx to v4.5.0.mdx and update the releases index
How to install update-release-notes
1Skills CLI (Vercel)
npx skills add tldraw/tldraw --skill update-release-notes -a claude-code2Manually: put the files in place
~/.claude/skills/update-release-notes/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/update-release-notes/
1Skills CLI (Vercel)
npx skills add tldraw/tldraw --skill update-release-notes -a codex2Manually: put the files in place
.agents/skills/update-release-notes/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add tldraw/tldraw --skill update-release-notes -a cursor2Manually: put the files in place
.cursor/skills/update-release-notes/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install tldraw/tldraw skills/update-release-notes2Manually: put the files in place
.github/skills/update-release-notes/SKILL.md1Skills CLI (Vercel)
npx skills add tldraw/tldraw --skill update-release-notes -a gemini-cli2Platform CLI
gemini skills install https://github.com/tldraw/tldraw --path skills/update-release-notesManually: put the files in place
.devin/skills/update-release-notes/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add tldraw/tldraw --skill update-release-notes -a opencodeClaude.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 update-release-notes
How to install update-release-notes in Claude Code?
Run npx skills add tldraw/tldraw --skill update-release-notes -a claude-code, the file will appear in ~/.claude/skills/update-release-notes/SKILL.md.
What does the update-release-notes skill do?
Maintains the release notes file in the tldraw repo: adds new PRs to next.mdx and archives it to a versioned file after a release. The skill operates on a local clone of tldraw/tldraw and uses git cherry to compare patches between branches.
Where does update-release-notes get the PR list from?
From the main branch (three weeks of development) or production (freeze week). In the first case, it compares against the last tag; in the second, against the previous release branch to include only hotfixes that reached production.