write-release-notes — Claude Code skill for release notes
Creates and reviews tldraw SDK release-note articles from merged PRs, with migration guidance for breaking changes.
npx skills add tldraw/tldraw --skill write-release-notes -a claude-codeWhat write-release-notes does
This skill defines a workflow for published tldraw SDK release notes. Release articles live in apps/docs/content/releases/: next.mdx collects upcoming changes, while files such as vX.Y.0.mdx hold published versions. It starts with release details from gh release view, then finds merged PRs through git log or gh pr list.
For each PR, the skill calls for title, body, labels, author, and branch details through gh pr view <PR_NUMBER> --json title,body,labels,author,baseRefName. Only PRs merged into main belong in the release. That filter matters because feature-branch work has not shipped yet.
It guides the article structure for major changes, API updates, improvements, fixes, and patch releases. Every breaking change needs a migration recipe, either as a dedicated section with before-and-after code or as an explicit replacement in an API entry. The final check covers PR links, contributor credits, and section order.
What it helps with
- find merged PRs between releases
- exclude PRs merged to feature branches
- create release articles under
apps/docs/content/releases/ - add migration steps for breaking API changes
- review patch releases for a minor version
Example prompts for the agent
- Draft tldraw SDK release notes for `v4.3.0` in `apps/docs/content/releases/`.
- Find the PRs between `v4.2.0` and `v4.3.0` and outline the release article.
- Review this release note and add migration recipes for every breaking change.
How to install write-release-notes
1Skills CLI (Vercel)
npx skills add tldraw/tldraw --skill write-release-notes -a claude-code2Manually: put the files in place
~/.claude/skills/write-release-notes/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/write-release-notes/
1Skills CLI (Vercel)
npx skills add tldraw/tldraw --skill write-release-notes -a codex2Manually: put the files in place
.agents/skills/write-release-notes/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add tldraw/tldraw --skill write-release-notes -a cursor2Manually: put the files in place
.cursor/skills/write-release-notes/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install tldraw/tldraw write-release-notes2Manually: put the files in place
.github/skills/write-release-notes/SKILL.md1Skills CLI (Vercel)
npx skills add tldraw/tldraw --skill write-release-notes -a gemini-cli2Platform CLI
gemini skills install https://github.com/tldraw/tldraw --path skills/write-release-notesManually: put the files in place
.devin/skills/write-release-notes/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add tldraw/tldraw --skill write-release-notes -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
From the same set7
The whole set →Similar
Questions about write-release-notes
How do I install write-release-notes in Claude Code?
Run npx skills add tldraw/tldraw --skill write-release-notes -a claude-code, then run npx skills add tldraw/tldraw --skill write-release-notes -a claude-code again. The skill file is located at ~/.claude/skills/write-release-notes/SKILL.md.
What does write-release-notes do?
It guides the creation and review of tldraw SDK release articles, from release and PR discovery through article structure and final checks.
How are breaking changes documented?
Each breaking change needs a migration recipe. Use a dedicated migration block for a featured change, or name the replacement and caveats directly in an API list entry.