gh-issue

name	gh-issue
description	Create GitHub Issue with structured description. Use when creating issue, reporting bug, requesting feature. Triggers on "/gh-issue", "create issue", "建立 issue", "報 bug", "feature request".
allowed-tools	Bash, Read, Glob, Grep
version	1.0.0
scope	public
evolution	{"enabled":true,"version":"1.0.0","stability":"stable","auto_evolve":"patch","created":"2026-01-18T00:00:00.000Z","updated":"2026-01-18T00:00:00.000Z","history":[]}

GH Issue - Create GitHub Issue

Create structured GitHub Issues, supporting Bug Report, Feature Request, Task, and other types.

---

Integrations

upstream:
  - context: User-described problem or requirement
    receives: Problem description, error messages, feature requirements

downstream:
  - skill: auto-cycle
    produces: Task ready for backlog
  - output: GitHub Issue
    produces: Trackable issue

---

Out of Scope

• Closing Issues - Only creates, does not close
• Assigning Assignees - Can be manually assigned after creation
• Modifying existing Issues - Only creates new Issues
• Cross-repo Issues - Only handles current repo

---

When to Use

Use cases:

• Found a bug that needs to be tracked
• Have a new feature idea that needs to be recorded
• Found an issue during code review that needs an issue
• Want to create task tracking

Not suitable for:

• Quick fixes (just fix it directly)
• An identical issue already exists

---

Issue Types

Type	Label	Template
Bug Report	bug	Includes reproduction steps, expected/actual results
Feature Request	enhancement	Includes use cases, proposed solution
Task	task	Simple task description
Documentation	documentation	Documentation improvement suggestions

---

Workflow

Phase 0: Pre-flight Checks

0. Verify environment before proceeding

   # Confirm inside a git repo
   git rev-parse --is-inside-work-tree
   
   # Confirm gh is authenticated
   gh auth status
   

   • If not a git repo: notify user and stop
   • If gh not authenticated: prompt gh auth login and stop

Phase 1: Determine Issue Type

1. Analyze user input

   Determine type based on keywords:

   Keywords	Type
   bug, error, broken, doesn't work	Bug Report
   want, wish, suggest, feature, add	Feature Request
   task, todo	Task
   docs, documentation, README	Documentation

2. If uncertain, ask the user

   What type of issue is this?
   1. Bug Report
   2. Feature Request
   3. Task
   4. Documentation
   

Phase 2: Gather Information

3. Information needed for Bug Report

   • Problem description
   • Reproduction steps
   • Expected result vs actual result
   • Environment info (optional)
   • Error messages (if any)

4. Information needed for Feature Request

   • Feature description
   • Use case / why it's needed
   • Proposed solution (optional)

5. Information needed for Task

   • Task description
   • Acceptance criteria (optional)

Phase 3: Generate Issue

6. Generate title

   Format: [type] short description

   Examples:

   • [bug] API times out under high concurrency
   • [feat] Support OAuth login
   • [task] Update dependencies to latest version

7. Generate content (by type)

   Bug Report:

   ## Problem Description
   
   [Describe the problem]
   
   ## Reproduction Steps
   
   1. Run XXX
   2. Click YYY
   3. See error
   
   ## Expected Result
   
   [What should happen]
   
   ## Actual Result
   
   [What actually happens]
   
   ## Environment
   
   - OS: macOS 15.0
   - Node: v20.x
   - Browser: Chrome 120
   
   ## Error Messages
   
   

   [Error messages]

   Feature Request:

   ## Feature Description
   
   [Describe the desired feature]
   
   ## Use Cases
   
   As a [role], I want [feature], so that [benefit].
   
   ## Proposed Solution
   
   [Optional: describe possible implementation]
   
   ## Alternative Approaches
   
   [Optional: other approaches considered]
   

Phase 4: Create Issue

8. Run gh issue create

   gh issue create \
     --title "[type] title" \
     --body "$(cat <<'EOF'
   ## Problem Description
   ...
   EOF
   )" \
     --label "bug"
   

9. Display results

   • Show Issue URL
   • Show Issue number

---

Implementation Checklist

Pre-execution checks:

• Current directory is a git repo
• gh is logged in
• Confirm no duplicate issues exist

Gather information:

• Determine issue type
• Collect necessary information
• If it's a bug, try to collect error messages

Generate Issue:

• Title is concise and clear
• Content is structured
• Correct label applied
• Run gh issue create

Completion confirmation:

• Issue created successfully
• Display Issue URL

---

Verification

Success Criteria

Issue Quality:

• Title includes type label
• Content structure is clear
• Has correct label
• Bug report has reproduction steps

Git Operation Success:

• gh issue create executed successfully
• Issue link is accessible

Verification Commands

# Confirm Issue has been created
gh issue list --author @me

# View Issue details
gh issue view [number]

# Open in browser
gh issue view [number] --web

---

Safety and Escalation

Situations to Stop Execution

Situation	Reason	Action
Not a git repo	Cannot determine target repo	Prompt to enter repo directory
gh not logged in	Cannot operate	Prompt to run gh auth login
No network connection	Cannot reach GitHub	Display error
Insufficient information	Cannot generate meaningful issue	Ask for more information

---

Issue Template Reference

Bug Report

## Problem Description

When [performing an action], the system [incorrect behavior].

## Reproduction Steps

1. Log in to the system
2. Navigate to XXX page
3. Click YYY button
4. Observe the error

## Expected Result

Should [correct behavior].

## Actual Result

Actually [incorrect behavior], displaying the following error:

Error: Cannot read property 'x' of undefined at someFunction (file.js:123)

## Environment

- OS: macOS 15.0
- Node: v20.10.0
- Browser: Chrome 120

---

Generated with Claude Code

Feature Request

## Feature Description

Would like to be able to [feature description].

## Use Cases

As a user, I want [feature], so that [benefit].

**Specific scenarios**:
- When I XXX, I need YYY
- The current workaround is ZZZ, but it's not convenient

## Proposed Solution

Can be implemented by:

1. Adding YYY option to XXX
2. Adding ZZZ API on the backend

## Alternative Approaches

Also considered:
- Option A: [description]
- Option B: [description]

Chose the proposed solution because [reason].

---

Generated with Claude Code

Task

## Task Description

[Describe the task to complete]

## Acceptance Criteria

- [ ] Criterion 1
- [ ] Criterion 2
- [ ] Criterion 3

## Related Resources

- [Link 1]
- [Link 2]

---

Generated with Claude Code

---

Example Usage

Example 1: Report a Bug

/gh-issue API times out under high concurrency

# Output:
# This looks like a Bug Report, let me gather more info...
#
# Questions:
# 1. What are the reproduction steps?
# 2. Is there an error message?
#
# [After user provides info]
#
# Issue created successfully
# https://github.com/owner/repo/issues/456
# #456 [bug] API times out under high concurrency

Example 2: Feature Request

/gh-issue Want to support OAuth login

# Output:
# Issue created successfully
# https://github.com/owner/repo/issues/457
# #457 [feat] Support OAuth login

---

Quick Start

# Report a Bug
/gh-issue Login feature is broken

# Feature Request
/gh-issue Want to add XXX feature

# Create a Task
/gh-issue task: Update README