Labsco
tldraw logo

pr

★ 48,500

by tldraw · part of tldraw/tldraw

Create or update a pull request for the current branch in the tldraw repository. Use when the user invokes pr, asks to create a PR, update an existing PR, push…

🔥🔥✓ VerifiedFreeQuick setup
#automation#git
🔒 Repo-maintenance skill. It exists to help maintain tldraw/tldraw itself — it's only useful if you contribute code to that project.

This is the playbook your agent receives when the skill activates — you don't need to read it to use the skill, but it's here to audit before installing.

by tldraw

Create or update a pull request for the current branch in the tldraw repository. Use when the user invokes pr, asks to create a PR, update an existing PR, push… npx skills add https://github.com/tldraw/tldraw --skill pr Download ZIPGitHub48.5k

PR

Create or update a pull request for the current branch.

Use ../write-pr/SKILL.md as the standards reference for PR titles, descriptions, release notes, API changes, code changes tables, and human-note preservation.

Workflow

  • Gather context:

  • Current branch: git branch --show-current

  • Working tree: git status --short

  • Existing PR: gh pr view --json number,title,url 2>/dev/null

  • Recent branch commits: git log main..HEAD --oneline 2>/dev/null || git log -3 --oneline

  • Prepare the branch:

  • If on main, create a new branch with a descriptive name.

  • Commit relevant changes, excluding secrets and explicitly private content.

  • Push the branch to the remote. Never force push.

  • If no PR exists, create one with gh pr create.

  • If a PR exists, read it with gh pr view --json title,body,labels,number and inspect the changed-file summary with gh pr diff --stat.

  • Update the title or body with gh pr edit if the existing PR does not match the current diff or the write-pr standards.

  • Search for related issues and link them in the PR description with Closes #123 or Relates to #123 where appropriate.

  • Share the PR URL with the user.

Handling problems

Committing automatically runs hooks. Fix formatting, lint, type, or import issues when the fix is mechanical.

If a hook failure requires meaningful product or implementation decisions, stop and ask the user how to proceed.

Never force commit or force push.

Rules

  • Follow ../write-pr/SKILL.md for all PR content standards.

  • Do not include AI attribution in commit messages, PR titles, or PR descriptions.

  • Do not add yourself or an AI tool as a co-author.