take

Implements GitHub issues in tldraw/tldraw and opens pull requests.

50.1k|3.5k|Updated May 9, 2021
One-click install
npx skills add https://github.com/tldraw/tldraw --skill take
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: take
Source: https://github.com/tldraw/tldraw/tree/main/skills/take
Command: npx skills add https://github.com/tldraw/tldraw --skill take

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Turning a GitHub issue into a merged pull request involves many manual steps: finding the issue, understanding requirements, assigning it, writing code, verifying changes, and opening a PR. This Skill automates that entire workflow for the tldraw/tldraw repository.

Core Features & Use Cases

  • Issue Discovery and Assignment: Find issues by number, URL, or keyword search using the GitHub CLI, then assign them to the current user.
  • Guided Implementation: Analyze issue requirements, detect blocking open questions, plan a checklist, and implement changes following existing repo patterns.
  • Verification and PR Creation: Run typecheck and lint checks, then open a pull request linked to the issue with a test plan.
  • Use Case: A maintainer says "take issue 1234" and the Skill fetches the issue, implements the fix on a new branch, runs yarn typecheck and yarn lint, and opens a PR with "Closes #1234".

Quick Start

Take issue number 1234 from tldraw/tldraw, implement it, and open a pull request.

Frequently Asked Questions about take

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I implement a GitHub issue automatically?

Reference the issue by number, URL, or description and the Skill fetches it with the GitHub CLI, plans an implementation checklist, makes the code changes on a new branch, runs verification checks, and opens a pull request linked to the issue.

How to find a GitHub issue by description instead of number?

The Skill searches open issues first using gh issue list with your search terms, then falls back to all issues if nothing matches. If several issues match, it asks you to choose; if none match, it offers to create a new issue.

What happens if an issue has unanswered questions or missing details?

Unanswered critical questions, unresolved awaiting-answer placeholders, or More Info Needed labels are treated as blockers. The Skill resolves them with you before implementing rather than guessing at unspecified behavior.

What verification runs before the pull request is created?

The Skill runs the smallest relevant checks first, typically yarn typecheck and yarn lint as final checks. For focused package changes, it prefers the relevant workspace tests before repo-wide checks.

Does this work with repositories other than tldraw/tldraw?

The workflow is written specifically for tldraw/tldraw, including its yarn-based checks and repo conventions. The general pattern could transfer, but commands and references target that repository.