메뉴
Use when the user wants to create a GitHub issue from a rough problem description or feature idea
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | create-issue |
| description | Use when the user wants to create a GitHub issue from a rough problem description or feature idea |
The user wants to create a GitHub issue. Their input is: $ARGUMENTS
If no description was provided, ask the user what the issue is about.
Follow these steps:
Investigate the codebase. Based on the user's description, search for relevant files, code patterns, and existing behavior related to the problem or feature. Understand enough context to write a well-informed issue.
Check for duplicates. Run gh issue list --state open --limit 30 and scan for existing issues that cover the same topic. If a likely duplicate exists, tell the user and ask how they want to proceed.
Draft the issue. Based on your investigation, prepare:
## Description
What the problem is or what the feature should do.
## Context
Relevant files, components, or architecture details you found in the codebase.
## Suggested approach
A brief outline of how this could be implemented or fixed, if applicable.
bug — Something isn't workingenhancement — New feature or requestdocumentation — Improvements or additions to documentationbite size — Nice, small, not too complexa bit bigger — Not very complex but has more system design considerationsarchitecturally complex — Requires careful consideration for correct architecturerequires investigation — Requires non-code investigation before deciding on actionfrontend — Related to frontendclaude config — Related to configuring Claude / AI assisted development workflowPresent the draft to the user. Show the full issue (title, body, label) and ask if they want to:
On approval, create the issue. Run:
gh issue create --title "<title>" --body "<body>" --label "<label>"
Show the resulting issue URL to the user.
Create a git commit with a short, lowercase commit message
Create a pull request with a structured description covering why, what, challenges, and future work
Analyze a GitHub issue and develop an implementation plan
Review all changes on the current branch compared to master
Review unstaged git changes for bugs, logic errors, and security problems
Review unstaged git changes for code style and architectural cleanliness