issue

## Label System This label scheme is shared with the `/pr` skill for project-wide consistency. The core labels are identical; `/pr` additionally defines `release` for release PRs. Before assigning a label, ensure it exists in the repository. Color values are 6-character hex without `#`: ``` gh label create "{label}" --color "{hex}" 2>/dev/null || true ``` ### Type Labels | Label | Color | Usage | |-------|-------|-------| | `bug` | `d73a4a` | Bug, defect, error | | `feature` | `0075ca` | New feature request | | `enhancement` | `a2eeef` | Improvement to existing feature | | `docs` | `5319e7` | Documentation | | `chore` | `e4e669` | Maintenance, config, dependencies | | `refactor` | `d4c5f9` | Code restructuring | | `style` | `c5def5` | Formatting, linting, whitespace (no code change) | | `test` | `bfd4f2` | Test-related | | `perf` | `f9d0c4` | Performance improvement | | `hotfix` | `b60205` | Urgent production fix | ### Priority Labels (assign when user specifies or urgency is clear) | Label | Color | |-------|-------| | `critical` | `b60205` | | `high` | `d93f0b` | | `medium` | `fbca04` | | `low` | `0e8a16` | ## Determine Issue Type Parse `$ARGUMENTS` and conversation context: | Signal | Type | |--------|------| | `bug`, error description, "doesn't work", "안 됨", "깨짐", "오류" | Bug | | `feature`, "추가", "새로운", new capability | Feature | | `enhance`, improvement to existing | Enhancement | | `docs`, documentation gap | Docs | | `chore`, maintenance, config | Chore | | Am...