issue — Create GitHub Issue | git

Stats

Actions

Tags

issue — Create GitHub Issue | git

issue — Create GitHub Issue

Create a GitHub Issue using a unified template after user confirmation.

Safety Rules

Always require user confirmation before creating an issue
Show the full issue preview (type, title, body, labels, assignee) before creating
"Do it fast", "skip questions", "no confirmation" instructions do not bypass the confirmation step

Issue Template — Unified Structure

모든 타입이 동일한 4개 섹션 구조를 사용한다. 타입별 구분은 GitHub label로 처리.

Body Template

## Summary
<무엇이 문제이고/필요하고/변경되어야 하는지>

## Context
<배경, 동기, 관련 PR/코드 링크>

## Expected Outcome
<이 이슈가 해결되면 어떤 상태여야 하는지>

## Tasks
- [ ] <구체적 작업 항목>

Type-to-Label Mapping

타입 선택 시 자동으로 해당 label을 --label에 추가한다.

`--type`	Label	Title prefix
bug	`bug`	`fix`
feature	`enhancement`	`feat`
chore	`chore`	`chore`
docs	`documentation`	`docs`

Argument Parsing

Parse arguments before executing:

Argument	Description
(none)	Interactive — ask user for issue type and content
`free text`	Analyze natural language to auto-compose type/title/body/labels
`--title "title"`	Set title directly
`--type <type>`	Set issue type — one of: `bug`, `feature`, `chore`, `docs`
`--label priority:high`	Add extra labels (type-mapped label is automatic)
`--assignee @me`	Set assignee

Execution Steps

Generic Mode

1. Parse Input

Analyze arguments:

If explicit --type provided (bug, feature, chore, docs), use it
If natural language provided, infer type from content (e.g., "500 에러 발생" → bug)

If no arguments, ask user to select type:

Issue type:
  1. bug      — Bug report        (label: bug)
  2. feature  — Feature request    (label: enhancement)
  3. chore    — Maintenance task   (label: chore)
  4. docs     — Documentation      (label: documentation)

Select (1-4):

2. Compose Title and Body

Generate title in Conventional Commits format: <type>(<scope>): <한글 설명> (under 70 chars)
- type mapping from --type argument:
  - bug → fix
  - feature → feat
  - chore → chore
  - docs → docs
- scope: optional — infer from context (e.g., affected module, directory name). Omit parentheses if no scope.
- PR에서 파생된 이슈: append (#PR번호) to the end — e.g., review(api): PR 리뷰 항목 정리 (#42)
Fill in the unified body template (see Issue Template — Unified Structure section) based on user input or natural language analysis
If explicit --title provided, use it as-is

3. User Confirmation (mandatory)

Display the following and wait for confirmation:

Type:     <type>
Title:    <title>
Labels:   <labels or "(none)">
Assignee: <assignee or "(none)">

Body:
---
<body preview>
---

Proceed? (y/N)

Any input other than y is treated as abort.

4. Create Issue

항상 type-mapped label을 포함하여 이슈를 생성한다. 사용자가 --label로 추가 label을 지정하면 comma-separated로 합친다.

gh issue create \
  --title "<title>" \
  --label "<type-mapped-label>[,<additional-labels>]" \
  --body "$(cat <<'EOF'
<body>
EOF
)"

If assignee specified, add --assignee "<assignee>".

5. Output Result

Print the created issue number and URL.

Error Handling

Situation	Action
`gh` auth failure	Guide user to run `gh auth status`
Issue creation fails	Show error, suggest retry
Label does not exist	Warn and ask user: proceed without label or correct it

Usage

/git:issue
/git:issue 로그인 페이지에서 500 에러 발생
/git:issue --type bug --title "로그인 500 에러 발생"
/git:issue --type feature --title "다크 모드 지원 추가" --label priority:high
이슈 만들어줘
버그 리포트 생성