메뉴
Find a GitHub issue in tldraw/tldraw, assign it, implement it, verify it, and open a pull request. Use when the user invokes take, asks to take an issue, implement an issue, work on an issue number or URL, or pick up an issue from a description.
| name | take |
| description | Find a GitHub issue in tldraw/tldraw, assign it, implement it, verify it, and open a pull request. Use when the user invokes take, asks to take an issue, implement an issue, work on an issue number or URL, or pick up an issue from a description. |
Find an issue in tldraw/tldraw, implement it, and open a pull request.
The user may reference an issue by number, URL, or description.
gh issue view 123 --repo tldraw/tldraw
gh issue list --repo tldraw/tldraw --search "dark mode" --state open --limit 10
gh issue list --repo tldraw/tldraw --search "dark mode" --state all --limit 10
If there is one clear match, proceed. If several issues match, ask the user to choose from issue numbers and titles. If none match, ask whether to create a new issue using the issue skill.
Read the full issue and comments. Identify:
Agent-drafted issues may include ## Confidence and ## Open questions sections. Treat any unanswered Critical: question, _Awaiting answer._ entry, or More Info Needed label as a blocker unless codebase exploration proves the intended behavior is unambiguous. Resolve blockers with the user before implementing; non-critical questions marked _Deferred by user; not blocking implementation._ may remain open.
If the issue lacks detail, explore the codebase before deciding whether implementation is safe.
Assign the issue to the current GitHub user. If someone else is already assigned, ask the user whether to proceed.
Create a concise implementation checklist based on:
Create a new branch from main.
Work through the checklist:
Run the smallest relevant checks first. Use broader checks when the change touches shared behavior.
Typical final checks:
yarn typecheck
yarn lint
For focused package changes, prefer the relevant workspace tests before repo-wide checks.
Use the pr skill.
Closes #<issue-number>.End with:
_Awaiting answer._ placeholders.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.
Create a GitHub issue in the tldraw repository from a user description, then mature it through follow-up questions. Use when the user invokes issue, asks to create an issue, report a bug, file a feature request, or answers follow-up questions for an issue created by this skill.
Reference standards for writing and maintaining GitHub issues in the tldraw repository. Use as supporting guidance when another skill or workflow needs issue title, body, type, label, or triage standards.
Migrate a project to a newer version of the tldraw SDK. Use when upgrading tldraw packages, fixing TypeScript errors after a tldraw upgrade, or when the user mentions tldraw migration.
Reference standards for writing pull request titles and descriptions in the tldraw repository. Use as supporting guidance when another skill or workflow needs PR content standards, not as the user-facing create/update PR workflow.
Writing release notes articles for tldraw SDK releases. Use when creating new release documentation, drafting release notes from scratch, or reviewing release note quality. Provides guidance on structure, voice, and content for release files in `apps/docs/content/releases/`.