Create Issue

Draft a focused title and body for a GitHub issue, then file it. Bug reports state reproduction steps and observed versus expected behavior.

Step 1: Gather Context

Determine what the issue is about from the conversation. When the subject is ambiguous, use AskUserQuestion to settle it before drafting.

List the repo's issue templates, read its labels, and search for an existing issue covering the same thing:

ls .github/ISSUE_TEMPLATE/ 2>/dev/null
gh label list --limit 100
gh issue list --search "<keywords>" --state all

When the issue goes to a repository other than the checkout, replace the ls with gh api repos/<owner>/<repo>/contents/.github/ISSUE_TEMPLATE, read the files it lists through the same API, and pass --repo <owner>/<repo> to the label list and the duplicate search.

When the target repository, the checkout included, has no .github/ISSUE_TEMPLATE folder of its own, list its owner's .github repository with gh api repos/<owner>/.github/contents/.github/ISSUE_TEMPLATE, whose files GitHub applies to a repository without that folder.

Treat an empty listing or a 404 as normal. When templates exist, read the one matching the kind of issue, and read .github/ISSUE_TEMPLATE/config.yml when present. Follow the template's structure and required sections, and apply the labels and title prefix the template declares. For a YAML issue form, render each field's attributes.label as a ### heading with the answer beneath, matching what the web form produces. When config.yml sets blank_issues_enabled: false, choose a template rather than filing a blank issue.

When the search surfaces a plausible duplicate, present it and use AskUserQuestion to confirm whether to file anyway.

Step 2: Run /github-voice Skill

Run the /github-voice skill to load writing style rules.

Step 3: Draft Title and Body

Draft the title and body. Output them as chat text so the user can review before anything is filed.

Step 4: Confirm and Create

Use AskUserQuestion for confirmation only. Generate a random tag so the body file is unique across sessions:

head -c 4 /dev/urandom | xxd -p

Write the drafted body to .turbo/issue/<tag>-body.md (using the printed tag) with the Write tool, then create the issue with gh issue create --body-file:

gh issue create --title "<TITLE>" --body-file .turbo/issue/<tag>-body.md --label "<LABEL>,<LABEL>"

Add --repo <owner>/<repo> when the issue goes to a repository other than the checkout. Repeat --label when the template sets several. Drop --label when no existing label fits. Set the issue type with --type <name> when a type is asked for or the template declares one; an issue type is a separate feature from a label, so applying a label of the same name leaves the request unmet. Do not set --assignee or --milestone unless the user explicitly asks.

Then use the TaskList tool and proceed to any remaining task.

Rules

• Don't reference .turbo/ content (filenames, acceptance criteria, step numbers, headings) in the title or body. .turbo/ is gitignored, so these references would be opaque to anyone reading without local copies.
• Create labels only when the user asks.