Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →tldraw/update-release-notes
Update the release notes file at `apps/docs/content/releases/next.mdx` in the tldraw/tldraw repo based on PRs since the previous release, or archive `next.mdx` to a versioned file when a new version is published.
Passed 17 of 21 test cases with the skill, and 4 of 21 without it.
and 25 more in the full report
17 fixed3 passed either way3 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 17 test cases the skill fixed. Same model, same prompt, with and without the skill.
Before publishing a new version of tldraw to NPM, what precheck command must return an empty diff to verify that next.mdx is identical on both critical branches?
| Checked | Without skill | With skill |
|---|---|---|
| Directs running git diff --stat origin/production origin/main -- apps/docs/content/releases/next.mdx to verify zero differences before launch. | Missed | Passed |
The instructions your model reads when the skill loads.
This skill handles the operational tasks of maintaining release notes in the tldraw/tldraw repo: adding new PR entries to next.mdx and archiving releases when a new version is published.
This skill runs from the tldraw-internal repo but operates on a local clone of tldraw/tldraw.
Before starting, clone the tldraw repo:
git clone https://github.com/tldraw/tldraw.git /tmp/tldraw
All scripts take the repo path as their first argument. Run script commands from the repository root by replacing <skill-dir> with the directory that contains this SKILL.md. All file edits happen in this clone. At the end, commit and push from the clone.
The SDK releases every four weeks. One week before launch, the SDK is frozen and a production branch is cut from main. During release week, only hotfixes are cherry-picked to production.
The release notes in next.mdx must ultimately reflect what ships on the production branch. However, during the ~3 development weeks before the freeze, we build up release notes from main so they're not empty. The status script detects which phase we're in based on the date of the last minor release:
source: "main", <3 weeks since last minor release): PRs are gathered from main since the last release tag. These are preliminary — some may not ship if they're reverted or if production cherry-picks differ.source: "production", 3+ weeks since last minor release): PRs are gathered from the production branch using git cherry against the previous release branch. Only PRs that landed before the freeze or were hotfixed onto production are included. Entries accumulated from main that aren't on production will be pruned.next.mdx itself also has to be on production before the release is published, not just describe it. prepack.ts generates the RELEASE_NOTES.md that ships inside the tldraw npm package from the checkout being published, using next.mdx as the entry for the version being released. production only moves by hotfix during the freeze, so a release-notes PR merged to main reaches it only if it also carries the dotcom-hotfix-please label (see step 10). The check before publishing is an empty diff:
git diff --stat origin/production origin/main -- apps/docs/content/releases/next.mdx
Run the status script to determine versions and diff branch:
<skill-dir>/scripts/get-changelog-status.sh /tmp/tldraw
test cases passed, vs 4 / 21 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.