write-issue

Standardize GitHub issue titles, labels, and metadata for the tldraw repository.

Updated Feb 6, 2026
One-click install
npx skills add https://github.com/seflless/tldraw-agent-claude-code-provider --skill write-issue-seflless
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: write-issue
Source: https://github.com/seflless/tldraw-agent-claude-code-provider/tree/main/.claude/skills/write-issue
Command: npx skills add https://github.com/seflless/tldraw-agent-claude-code-provider --skill write-issue-seflless

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Streamlines and standardizes GitHub issue management for the tldraw repository, reducing ambiguity and manual cleanup.

Core Features & Use Cases

  • Enforces consistent issue titles and body formats to improve searchability and triage.
  • Defines and applies standard issue types, labels, and metadata to support scalable project governance.
  • Use Case: When triaging a high-volume backlog, apply the guidelines to quickly categorize and update issues.

Quick Start

Create a new issue following the defined title and label conventions, then update the issue to reflect standardized metadata.

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 titles and labels for consistent triage?

To standardize GitHub issue triage, enforce consistent title conventions, body formats, and predefined label sets. This standardized metadata categorizes issues systematically, reducing ambiguity and manual cleanup during high-volume backlog triage.

What is the best way to manage a high-volume GitHub issue backlog?

Managing a high-volume GitHub issue backlog requires a repeatable triage process with enforced conventions. Applying standard issue types and labeling guidelines supports scalable project governance by quickly categorizing and updating inconsistencies.

Does this GitHub issue workflow apply to any repository or just specific projects?

This GitHub issue workflow specifically applies to the tldraw repository. The enforced title conventions and labeling guidelines are tailored to maintain consistency and support scalable issue governance across that specific project environment.

How do I enforce consistent body formats when creating GitHub issues?

To enforce consistent body formats when creating GitHub issues, implement standardized creation guidelines. Defining standard issue types and metadata ensures new issues follow required conventions before triage, improving overall searchability.

Why does my GitHub issue triage process lack consistency across a project?

GitHub issue triage lacks consistency due to undefined title conventions and unstandardized metadata. Implementing enforced labeling guidelines and a repeatable triage process eliminates ambiguity, maintaining consistent project governance.