write-pr — Claude Code skill: what it does, how to install
Sets PR title and description standards: semantic types, structured templates, and reviewer-focused writing rules.
npx skills add tldraw/tldraw --skill write-pr -a claude-codeWhat write-pr does
The skill enforces PR formatting standards from the tldraw repository. Titles follow Conventional Commits: type (feat, fix, refactor, docs, perf, test, chore), optional scope (editor, sync), and a short description. Descriptions use two templates: bugs and improvements get a before–after–what-changed structure, everything else gets a motivation paragraph, change type checklist, test plan, and release notes.
Presentation rules: start with the goal and context, move from high-level to specifics, do not restate the diff line by line. The skill does not invent reasons for changes — you supply the context, it structures the presentation. This is tldraw's house style, taken from their working process: short, to the point, the reviewer should understand the intent before reading the code.
What it helps with
- standardize PR titles across a team using Conventional Commits
- structure a bug description: what it was, what it is, why
- write motivation for a reviewer without restating the code
- pick the right commit type (feat, fix, refactor) and scope
- format change type checklist and test plan
Example prompts for the agent
- write a PR description for this bug using write-pr template
- check this PR title: `feat(editor): add snap threshold` — does it match write-pr
- draft the before–after section for an improvement following write-pr
How to install write-pr
1Skills CLI (Vercel)
npx skills add tldraw/tldraw --skill write-pr -a claude-code2Manually: put the files in place
~/.claude/skills/write-pr/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/write-pr/
1Skills CLI (Vercel)
npx skills add tldraw/tldraw --skill write-pr -a codex2Manually: put the files in place
.agents/skills/write-pr/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add tldraw/tldraw --skill write-pr -a cursor2Manually: put the files in place
.cursor/skills/write-pr/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install tldraw/tldraw write-pr2Manually: put the files in place
.github/skills/write-pr/SKILL.md1Skills CLI (Vercel)
npx skills add tldraw/tldraw --skill write-pr -a gemini-cli2Platform CLI
gemini skills install https://github.com/tldraw/tldraw --path skills/write-prManually: put the files in place
.devin/skills/write-pr/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add tldraw/tldraw --skill write-pr -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
From the same set7
The whole set →Similar
Questions about write-pr
How to install write-pr in Claude Code?
Run npx skills add tldraw/tldraw --skill write-pr -a claude-code. The skill will appear in ~/.claude/skills/write-pr/SKILL.md.
What does write-pr do?
Sets PR title format (type, scope, description) and two description templates: bugs and improvements get a before–after structure, everything else gets a motivation paragraph and checklists. Rules require writing for the reviewer, not restating the diff.
When should I use write-pr templates?
When the team has agreed on these standards or you are working in the tldraw repository. The skill does not invent motivation — you provide the context, it structures the presentation.
