name	create-issue
description	Create a GitHub issue. Analyzes git diff automatically if no arguments provided, or uses the given context to create an issue.
disable-model-invocation	true
argument-hint	[optional: issue context or description]
allowed-tools	Bash, Read, Glob, Grep, AskUserQuestion

Create GitHub Issue

You are creating a GitHub issue for the current repository.

Check if arguments were provided: $ARGUMENTS

Run git diff and git status to analyze current uncommitted changes
Run git diff --cached to check staged changes
Run git log --oneline -5 to understand recent commit context
Based on the analysis, determine:
- Issue type: feat, fix, refactor, docs, chore, etc.
- A concise title summarizing the change
- A detailed body describing the problem and proposed solution

Use the provided arguments as context/description for the issue
Optionally read relevant files or run git diff if the context references code changes
Craft a clear title and detailed body based on the provided context

Before creating, show the user the draft title and body using a summary message
Ask the user for confirmation using AskUserQuestion with options: "Create as-is", "Edit title", "Edit body", "Cancel"

If confirmed, run:

gh issue create --title "<title>" --body "<body>"

Title should follow conventional format: type: short description (e.g., feat: add server lifecycle management)
Body should include relevant sections like ## Problem, ## Proposed Solution, or ## Changes as appropriate
Keep the title under 72 characters
Use markdown formatting in the body
Do NOT add labels or assignees unless the user explicitly requests them

name	create-issue
description	Create a GitHub issue. Analyzes git diff automatically if no arguments provided, or uses the given context to create an issue.
disable-model-invocation	true
argument-hint	[optional: issue context or description]
allowed-tools	Bash, Read, Glob, Grep, AskUserQuestion

You are creating a GitHub issue for the current repository.

Check if arguments were provided: $ARGUMENTS

Run git diff and git status to analyze current uncommitted changes
Run git diff --cached to check staged changes
Run git log --oneline -5 to understand recent commit context
Based on the analysis, determine:
- Issue type: feat, fix, refactor, docs, chore, etc.
- A concise title summarizing the change
- A detailed body describing the problem and proposed solution

Use the provided arguments as context/description for the issue
Optionally read relevant files or run git diff if the context references code changes
Craft a clear title and detailed body based on the provided context

Before creating, show the user the draft title and body using a summary message
Ask the user for confirmation using AskUserQuestion with options: "Create as-is", "Edit title", "Edit body", "Cancel"

If confirmed, run:

gh issue create --title "<title>" --body "<body>"

Title should follow conventional format: type: short description (e.g., feat: add server lifecycle management)
Body should include relevant sections like ## Problem, ## Proposed Solution, or ## Changes as appropriate
Keep the title under 72 characters
Use markdown formatting in the body
Do NOT add labels or assignees unless the user explicitly requests them

create-issue