Write Issue

Create well-structured GitHub issues that get results

✨ The solution you've been looking for

Verified
Tested and verified by our team
44568 Stars

Writing and maintaining GitHub issues for the tldraw repository. Use when creating new issues, editing issue titles/bodies, triaging issues, or cleaning up issue metadata (types, labels).

github issue-management triage documentation project-management bug-tracking feature-requests tldraw
Repository

See It In Action

Interactive preview & real-world examples

Live Demo
Skill Demo Animation

AI Conversation Simulator

See how users interact with this skill

User Prompt

Help me create a GitHub issue for a bug where arrow bindings break when shapes are rotated in tldraw

Skill Processing

Analyzing request...

Agent Response

A properly formatted issue with descriptive title, bug type, clear reproduction steps, and expected vs actual behavior

Quick Start (3 Steps)

Get up and running in minutes

1

Install

claude-code skill install write-issue

claude-code skill install write-issue
2

Config

3

First Trigger

@write-issue help

Commands

CommandDescriptionRequired Args
@write-issue bug-report-creationTransform a vague bug report into a well-structured GitHub issue with proper title, type, and detailed reproduction stepsNone
@write-issue feature-request-documentationStructure feature requests with clear problem statements, proposed solutions, and use casesNone
@write-issue issue-triage-and-cleanupClean up existing issues by fixing titles, setting proper types, and adding appropriate labelsNone

Typical Use Cases

Bug Report Creation

Transform a vague bug report into a well-structured GitHub issue with proper title, type, and detailed reproduction steps

Feature Request Documentation

Structure feature requests with clear problem statements, proposed solutions, and use cases

Issue Triage and Cleanup

Clean up existing issues by fixing titles, setting proper types, and adding appropriate labels

Overview

Writing and maintaining GitHub issues

Standards for issues in tldraw/tldraw.

Title standards

  • Sentence case - Capitalize only the first word and proper nouns
  • No type prefixes - Use GitHub issue types, not Bug:, Feature:, [Bug], etc.
  • Imperative mood for enhancements - “Add padding option” not “Adding padding option”
  • Descriptive for bugs - Describe the symptom: “Arrow bindings break with rotated shapes”
  • Specific - Readable without opening the issue body

Good titles

  • Arrow bindings break with rotated shapes
  • Add padding option to zoomToFit method
  • Pinch zoom resets selection on Safari

Bad titles

  • Bug: arrow bug (prefix, vague)
  • [Feature] Add new feature (prefix, vague)
  • Not working (vague)

Title cleanup transformations

  1. Remove prefixes: Bug: X → X
  2. Fix capitalization: Add Padding Option → Add padding option
  3. Use imperative: Adding feature X → Add feature X
  4. Be specific: Problem → [Describe the actual problem]
  5. Translate non-English titles to English

Issue types

Set via the GitHub GraphQL API after creating the issue (the --type flag is not reliably supported):

TypeUse for
BugSomething isn’t working as expected
FeatureNew capability or improvement
ExampleRequest for a new SDK example
TaskInternal task or chore

Labels

Use sparingly (1-2 per issue) for metadata, not categorization.

Common labels

LabelUse for
good first issueWell-scoped issues for newcomers
More Info NeededRequires additional information
sdkAffects the tldraw SDK
dotcomRelated to tldraw.com
a11yAccessibility
performancePerformance improvement
apiAPI change

Automation labels (do not apply manually)

keep, stale, update-snapshots, publish-packages, major, minor, skip-release, deploy triggers

Issue body standards

Bug reports

  1. Clear description of what’s wrong
  2. Steps to reproduce
  3. Expected vs actual behavior
  4. Environment details (browser, OS, version) when relevant
  5. Screenshots/recordings when applicable

Feature requests

  1. Problem statement - What problem does this solve?
  2. Proposed solution - How should it work?
  3. Alternatives considered
  4. Use cases

Example requests

  1. What API/pattern to demonstrate
  2. Why it’s useful
  3. Suggested approach
  4. Which example category it belongs to

Triage workflow

New issues

  1. Verify sufficient information to act on
  2. Set appropriate issue type
  3. Clean up title if needed
  4. Add More Info Needed label and comment if details missing
  5. Add good first issue if appropriate

Stale issues

  1. Review if still relevant
  2. Close if no longer applicable
  3. Add keep label if should remain open
  4. Request updates if waiting on information

Important

  • Never include “Generated with Claude Code” unless the PR directly relates to Claude Code
  • Never use title case for descriptions - use sentence case

What Users Are Saying

Real feedback from the community

Environment Matrix

Dependencies

GitHub repository access
GitHub GraphQL API access for issue types

Framework Support

tldraw SDK ✓ (primary focus) GitHub Issues API ✓

Context Window

Token Usage ~1K-3K tokens for standard issue creation and triage

Security & Privacy

Information

Author
tldraw
Updated
2026-01-30
Category
productivity-tools

Related Skills

Write Issue

Writing and maintaining GitHub issues for the tldraw repository. Use when creating new issues, …

View Details →

Github Issues

Create, update, and manage GitHub issues using MCP tools. Use this skill when users want to create …

View Details →

Github Issues

Create, update, and manage GitHub issues using MCP tools. Use this skill when users want to create …

View Details →