create_issue

Use this skill whenever creating a GitHub Issue.

Metadata to gather

Before creating the issue, determine:

• type: feat, fix, chore, docs, or test
• title: short imperative description
• priority: high, medium, or low
• area: existing repo area label or plain body metadata
• size: XS, S, M, L, or XL
• references: related issues, PRs, ADRs, docs, designs, logs, or external links
• dependencies: blocked-by, parent, or follow-up relationships
• acceptance criteria: concrete checklist items

If type, title, priority, area, size, or acceptance criteria are not clear from context, ask the user before proceeding.

Rules

• Use .claude/scripts/create_issue.sh; do not call gh issue create directly unless the script cannot satisfy the case.
• Do not invent labels. The script may create priority and size labels, but area labels are repository-specific.
• Store relationships that GitHub does not support portably in markdown sections.
• The script writes Definition of Ready/Done defaults so issues created from this skill satisfy the scaffolded issue-validation workflow.
• Check for duplicate issues before creating a new one:

  gh issue list --state open --search "<keywords>"
  

Create

Run:

.claude/scripts/create_issue.sh <type> "<title>" \
  --priority <high|medium|low> \
  --area "<area>" \
  --size <XS|S|M|L|XL> \
  --reference "<reference>" \
  --dependency "<dependency>" \
  --acceptance "<criterion>"

Repeat --reference, --dependency, and --acceptance as needed.

Report

After creation, report the issue number and URL:

gh issue view <number> --json url -q .url