Create a GitHub Issue

Extracts context from the current conversation, drafts a well-structured GitHub issue, and creates it after user confirmation.

Issue Structure

# [tag]: Brief summary of the issue

## Description

What the issue is about — the problem, the affected area, and why it matters.

## Steps to Reproduce

(For bug reports only)
Minimal steps to trigger the problem.

## Proposed Solution

(Optional — include when an implementation approach is known)
Outline of the planned changes, including which files will be modified, added, or removed.

## Related PR

(Include when a Proposed Solution is provided)
TBD — will be updated when the PR is created.

Choosing a Tag

Check whether the project defines its own tag list (common locations: docs/git-msg-tags.md, CONTRIBUTING.md). If none is found, use these defaults:

For issues that don't fit a standard tag, use descriptive labels like [bug report], [feature request], or [improvement].

When the issue includes a concrete implementation plan in its Proposed Solution, prefix the tag with [plan] — for example, [plan][feat]: Add webhook support.

Workflow

1. Gather Context

Review the conversation to determine:

• •Issue type: bug, feature, improvement, or planned work
• •Key details: what, why, which modules are involved
• •If a plan already exists in the conversation, use it as the Proposed Solution

2. Select the Tag

• •Read the project's tag file if one exists
• •Match the issue type to the most fitting tag
• •If ambiguous, present 2–3 options and let the user choose

3. Draft the Issue

Compose the issue following the structure above:

• •Title: [tag]: Summary — keep the summary under 80 characters
• •Description: Enough context for someone unfamiliar with the conversation to understand the problem
• •Steps to Reproduce: Only for bugs; keep it minimal
• •Proposed Solution: If a plan exists, include it verbatim — do not rewrite it
• •Related PR: Placeholder if a Proposed Solution is provided

4. Confirm with the User

Display the full draft and wait for explicit approval before creating anything.

5. Create the Issue

gh issue create --title "TITLE" --body-file - <<'EOF'
BODY
EOF

To update an existing issue instead (when invoked with --update <number>):

gh issue edit <number> --title "TITLE" --body-file - <<'EOF'
BODY
EOF

Display the resulting issue URL.

6. Handle Errors

Ownership

The issue is created on behalf of the user. The AI agent must not add any authorship or co-authorship attribution.