write-issue

Standardize GitHub issue titles, bodies, labels, and triage for tldraw.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill standardizes the creation and maintenance of GitHub issues for the tldraw repository, reducing ambiguity and ensuring consistent problem statements, reproduction steps, and metadata across contributors.

Core Features & Use Cases

  • Title & Body Standards: Enforces concise, descriptive titles and well-structured, reproducible issue bodies.
  • Labels & Metadata: Guides consistent labeling, types, and triage-ready metadata cleanup.
  • Triaging & Maintenance: Supports efficient issue triage, reassignment, and backlog hygiene across projects.

Quick Start

Example: Create or update an issue with a clear title like "Arrow bindings fail when dragging multiple selections" and a body that includes reproduction steps, expected vs actual behavior, and notes. Assign labels such as "bug", "sdk", and "needs-triage" as appropriate.

Frequently Asked Questions about write-issue

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

FAQPage Schema
How do I standardize GitHub issue formatting for bugs and features?

To standardize GitHub issue formatting, enforce concise descriptive titles, structured bodies with reproduction steps, and consistent labels like bug or feature. This ensures metadata hygiene and clear problem statements across contributor submissions.

What is the best way to triage GitHub issues and clean up backlog metadata?

The best way to triage GitHub issues is to apply predefined labels like needs-triage, verify reproduction steps, and update metadata. This maintains backlog hygiene by guiding consistent reassignment and categorization across maintenance tasks.

What should a GitHub issue body include for reliable bug reproduction?

A GitHub issue body should include clear reproduction steps, expected versus actual behavior, and relevant notes. Structuring content this way reduces ambiguity and ensures consistent problem statements for maintainers.

How do I write a descriptive GitHub issue title for SDK problems?

Write descriptive GitHub issue titles by summarizing the specific failure concisely, such as noting that arrow bindings fail when dragging multiple selections. Clear title formatting ensures immediate context for triage and maintenance.

When do I need to assign needs-triage and sdk labels to GitHub issues?

Assign needs-triage and sdk labels to GitHub issues when submitting bug reports that require maintainer evaluation and SDK component categorization. Consistent labeling supports efficient issue triage and accurate metadata cleanup across projects.