write-issue

Standardizes issue titles, bodies, types, labels, and triage for local and GitHub trackers.

2|Updated Sep 14, 2026
One-click install
npx skills add https://github.com/kwanpham2195/agent-stuff --skill write-issue-kwanpham2195
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: write-issue
Source: https://github.com/kwanpham2195/agent-stuff/tree/main/skills/write-issue
Command: npx skills add https://github.com/kwanpham2195/agent-stuff --skill write-issue-kwanpham2195

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Inconsistent issue titles, vague bug reports, and ad-hoc labeling make trackers hard to scan and triage. This Skill provides shared content standards so every issue—local or on GitHub—follows the same title, body, type, and label conventions. ## Core Features & Use Cases - Title standards: Enforces sentence case, imperative mood, no type prefixes, and specific wording, with cleanup transformations for existing titles. - Structured issue bodies: Defines templates for bug reports, feature requests, example requests, and request-intake issues with problem readbacks, open questions, and confidence lines. - GitHub triage workflow: Covers issue types set via the GraphQL API, label usage rules, and procedures for new and stale issues. - Use Case: When filing a bug about a broken UI interaction, apply the standards to produce a symptom-focused title like "Pinch zoom resets selection on Safari" with reproduction steps and expected versus actual behavior. ## Quick Start Write a GitHub issue for the login timeout bug following the write-issue standards for title, body, and type.

Frequently Asked Questions about write-issue

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

FAQPage Schema
How do I write a good GitHub issue title?▼

Use sentence case, imperative mood for enhancements, and describe the symptom for bugs without prefixes like "Bug:" or "[Feature]". A good title is specific enough to understand without opening the issue body.

How do I set a GitHub issue type like Bug or Feature?▼

Set the issue type via the GitHub GraphQL API after creating the issue, since the --type flag is not reliably supported. Available types include Bug, Feature, Example, and Task.

What should a bug report issue body include?▼

Include a clear description of what is wrong, steps to reproduce, expected versus actual behavior, environment details when relevant, and screenshots or recordings when applicable.

Can these issue standards be used without GitHub?▼

Yes, the content standards apply to local issues as well. Local mode uses the metadata and lifecycle from the companion issue skill and never requires GitHub, the gh CLI, or network access.

Which labels should I avoid applying manually on GitHub issues?▼

Avoid automation labels such as keep, stale, update-snapshots, publish-packages, major, minor, skip-release, and deploy triggers. Use labels sparingly, one or two per issue, for metadata rather than categorization.