take
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.
What this skill does
# Take Find an issue in `tldraw/tldraw`, implement it, and open a pull request. ## Workflow ### 1. Find the issue The user may reference an issue by number, URL, or description. - For a number or URL, fetch the issue directly: ```bash gh issue view 123 --repo tldraw/tldraw ``` - For a description, search open issues first: ```bash gh issue list --repo tldraw/tldraw --search "dark mode" --state open --limit 10 ``` - If no open issue matches, search all issues: ```bash 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. ### 2. Understand the issue Read the full issue and comments. Identify: - Issue type: bug, feature, enhancement, cleanup, docs, or task. - Requested behavior and acceptance criteria. - Technical notes and affected files. - Relevant discussion or clarifications. 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. ### 3. Assign the issue Assign the issue to the current GitHub user. If someone else is already assigned, ask the user whether to proceed. ### 4. Plan the implementation Create a concise implementation checklist based on: - The issue description. - Acceptance criteria. - Codebase exploration. - Existing repo patterns. ### 5. Implement Create a new branch from `main`. Work through the checklist: - Read files before editing them. - Follow existing patterns. - Keep changes focused on the issue. - Avoid speculative improvements. - Update docs, examples, tests, or API reports when the issue requires it. ### 6. Verify Run the smallest relevant checks first. Use broader checks when the change touches shared behavior. Typical final checks: ```bash yarn typecheck yarn lint ``` For focused package changes, prefer the relevant workspace tests before repo-wide checks. ### 7. Create the PR Use the `pr` skill. - Link the issue with `Closes #<issue-number>`. - Include relevant context from the issue discussion. - Include a clear test plan. ### 8. Summarize End with: - Issue implemented. - Key changes and files modified. - Verification performed. - PR link. - Manual testing steps, if relevant. - Any acceptance criteria that could not be met and why. ## Rules - Ask the user when requirements are unclear. Do not implement past unanswered critical questions or unresolved `_Awaiting answer._` placeholders. - Do not guess at unspecified product behavior. - Keep the implementation scoped to the issue. - Never include AI attribution in commits, issues, or PRs.
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.