skills.rest
arusinova
arusinovaCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

write-issue

Standardize GitHub issue titles, types, labels, and triage workflows.

Updated Aug 23, 2026
Search Tags:#workflow#github#standards#issue#triage#labels
One-click install
npx skills add https://github.com/arusinova/annarusinova-platform --skill write-issue-arusinova
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: write-issue
Source: https://github.com/arusinova/annarusinova-platform/tree/main/.claude/skills/write-issue
Command: npx skills add https://github.com/arusinova/annarusinova-platform --skill write-issue-arusinova

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Issues in the tldraw/tldraw project often suffer from inconsistent titles, unclear triage, and scattered labels, which slows down feedback loops and resolution times. This Skill defines a standard workflow for creating, editing, and triaging issues to improve clarity and collaboration.

Core Features & Use Cases

  • Standardized title formatting: remove prefixes, proper capitalization, and imperative mood to ensure concise, actionable descriptions.
  • Issue type and labeling guidance: guidance on when to use Bug, Feature, or Task types and how to apply common labels to accelerate triage and routing.
  • Triage workflow: a repeatable process for validating, enriching, and routing issues, reducing back-and-forth and enabling faster prioritization.

Quick Start

Follow the standard issue guidelines when creating a new GitHub issue to ensure consistent titles, types, and labeling.

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 for consistent triage?▼

Standardize GitHub issue titles by removing prefixes, applying proper capitalization, and using imperative mood to ensure concise, actionable descriptions that accelerate triage routing and feedback loops.

What is the best way to triage GitHub issues with consistent labels?▼

The best way to triage GitHub issues is following a repeatable process for validating, enriching, and routing issues using standardized types like Bug, Feature, or Task to enable faster prioritization.

When should I use Bug, Feature, or Task labels on GitHub issues?▼

Use Bug, Feature, or Task labels on GitHub issues when categorizing the core problem type during creation and triage to accelerate routing, prioritization, and backlog management across the repository.

Does this issue triage workflow apply to contributors and maintainers?▼

Yes, this issue triage workflow applies to both maintainers and contributors who manage the repository backlog, prioritization, and triage processes to improve clarity and collaboration.

Why does inconsistent GitHub issue formatting slow down resolution?▼

Inconsistent GitHub issue formatting slows down resolution because unclear titles, scattered labels, and undefined triage steps create feedback loop delays and prevent efficient backlog routing.

Related Skills

Explore More Software Engineering Skills→
tomzxtomzx
5

onboard-repository

Bootstrap repository onboarding with SDLC structure and automated issue triage workflows.

Community
Advanced
cliffthelincliffthelin

triage

Apply type, effort, priority, and area labels to GitHub issues.

Community
Intermediate
amo-tech-aiamo-tech-ai

cicd-pipeline

Automate GitHub Actions CI/CD pipelines for build, test, lint, and deployment workflows.

Community
Intermediate
jupesjupes
2

github-triage

Automate GitHub issue triage with a label-based state machine.

Community
Advanced