Issue

Create a GitHub issue from a short description.

Conventions

• Title: Conventional Commit format (type(scope): description), under 60 chars, no trailing period
• Label: enhancement for features, bug for bugs
• Body sections (in order): What would you like?, Motivation, Proposed approach, Scope
• Each section is a ## heading followed by 1-3 short paragraphs
• Write plainly — no code blocks, no bullet-heavy lists, no implementation detail
• Focus on what and why, not how — leave implementation to the branch
• Scope section uses a flat bullet list of affected areas

Workflow

1. Understand the idea: read the user's description carefully — ask if intent is unclear
2. Check for duplicates: run gh issue list --state open --limit 50 and scan for overlap
3. Draft the issue: write title and body following the conventions above