메뉴
Run when the user asks for skill-issue, /issue, or to create a GitHub issue from Todam templates and an active plan.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Run when the user asks for skill-review, /review, or to check Todam implementation drift against an active execution plan.
Run when the user asks for skill-pr, /pr, or to create a Todam pull request from the current branch.
Run when the user asks for skill-commit, /commit, or to split and commit Todam changes using the repository commit convention.
Run when the user asks for skill-complete, /complete, or to move a Todam active execution plan to completed after all status checks pass.
Run when the user asks for skill-impl, /impl, /impl <feature> be, /impl <feature> fe, or to implement a Todam active execution plan.
Run when the user asks for skill-plan, /plan, or to create a Todam execution plan from requirements, feature specs, and API contracts.
| name | skill-issue |
| description | Run when the user asks for skill-issue, /issue, or to create a GitHub issue from Todam templates and an active plan. |
Create a GitHub issue from .github/ISSUE_TEMPLATE/.
Parse arguments as <feature description> [feature|bugfix|refactore|deploy]; default type is feature.
Read .github/ISSUE_TEMPLATE/<type>.yml.
If an active plan exists at docs/exec-plans/active/<feature>.md, derive tasks from that plan.
Draft the issue title and body from the template. Title follows the template title prefix (e.g. [Feature] 제목). Do not inflate tasks beyond the spec/plan.
Labels: pick one or more from the fixed list below that match the actual work. Do not be bound to the template default label; choose by real task content. Never invent labels outside this list.
⚙ Setting — 개발 환경 세팅✨ Feature — 기능 개발🎨 Html&css — 마크업 & 스타일링🐞 BugFix — Something isn't working💻 CrossBrowsing — 브라우저 호환성📃 Docs — 문서 작성 및 수정📬 API — 서버 API 통신🔨 Refactor — 코드 리팩토링🙋♂️ Question — Further information is requested🥰 Accessibility — 웹접근성 관련✅ Test — test 관련(storybook, jest...)🌏 Deploy — 배포 관련Assignee: infer from the plan Owner (BE/FE etc.) and git user (git config user.name) / recent commit author. If uncertain, assign the git user and state the inference basis in the draft for confirmation.
Show the draft (title, body, labels, assignee) and wait for approval.
After approval, run gh issue create with --label and --assignee flags.
Respond briefly after execution:
성공: <생성한 이슈 URL>실패: <실패한 workflow 단계와 이유>Success/failure is based on issue workflow completion, not Supabase insert success.