// Create and research a GitHub issue in the tldraw repository from a user description. Use when the user invokes issue, asks to create an issue, report a bug, file a feature request, or add research to a new issue.
| name | issue |
| description | Create and research a GitHub issue in the tldraw repository from a user description. Use when the user invokes issue, asks to create an issue, report a bug, file a feature request, or add research to a new issue. |
Create a GitHub issue on tldraw/tldraw from a user description, then research it.
Use ../write-issue/SKILL.md as the standards reference for issue titles, bodies, types, labels, and triage conventions.
git branch --show-current.gh issue list --repo tldraw/tldraw --limit 5 --json number,title --jq '.[] | "#\(.number) \(.title)"'.localhost:5420 from yarn dev.localhost:3000 from yarn dev-app.localhost:3001 from yarn dev-docs.../write-issue/SKILL.md.gh issue create --repo tldraw/tldraw --title "..." --body "..."
gh issue create --type is not reliable across versions.Improve developer resources for examples, documentation, comments, starter kits, and npm create tldraw.Improve automations for GitHub Actions, review bots, CI/CD, and automation work.gh issue comment <issue-number> --repo tldraw/tldraw --body "..."
../write-issue/SKILL.md for all issue content 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/`.
Create a narrated video walkthrough of a pull request with code slides and audio narration. Use when asked to create a PR walkthrough, PR video, or walkthrough video.
Reimplement the current branch on a new branch with a clean, narrative-quality git commit history. Use when asked to make a clean copy branch, clean up commit history by replaying work, or rebuild a branch as reviewable commits.
Create a git commit for the current changes. Use when asked to commit changes, make a commit, generate a commit message, or commit the current worktree with optional user-provided context.