メニュー
Fetches and analyzes a GitHub issue for the Rels repo, then maps it to an actionable work plan. Use this skill when asked to "이슈 분석해줘", "이슈 #N 봐줘", "이슈 보고", "어떤 작업인지 알려줘", or before starting work on a reported issue.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Fetches PR review comments for the Rels repo, applies the requested code changes, and posts reply comments confirming each fix. Use this skill when asked to "리뷰 반영해줘", "코멘트 처리해줘", "PR 리뷰 답글 달아줘", "리뷰 코멘트 적용해줘", or "review 반영".
Implements Next.js pages under src/app/ for Rels. Use this skill when writing new pages, modifying existing pages, or integrating user flows. Used by the rels-feature-builder agent.
Creates a GitHub Pull Request for the Rels repo following the project PR template. Use this skill when asked to "PR 만들어줘", "PR 올려줘", "pull request 생성", "PR 작성해줘". Fills in the Korean PR template, determines the type prefix for the title from the branch commits, and runs gh pr create.
Stages and commits changes in the Rels repo following the project commit convention. Use this skill when asked to "커밋해줘", "commit", "변경사항 커밋", "저장해줘", or after finishing a feature/fix and needing to commit. Splits changes into granular logical units and commits each separately with a Korean message.
Writes TanStack Query hooks and API types for Rels. Use this skill when writing new entity hooks, adding queryKeys, adding apiUrls, or modifying existing hooks. Used by the rels-api-architect agent.
Writes shared UI components and SVG icons for Rels. Use this skill when adding or modifying components under src/components/common/ or src/assets/svg/. Used by the rels-component-writer agent.
| name | rels-issue-analysis |
| description | Fetches and analyzes a GitHub issue for the Rels repo, then maps it to an actionable work plan. Use this skill when asked to "이슈 분석해줘", "이슈 #N 봐줘", "이슈 보고", "어떤 작업인지 알려줘", or before starting work on a reported issue. |
gh issue view {N} --json title,body,labels,assignees,comments
If no issue number is given, list open issues first:
gh issue list --state open --limit 20
Identify:
Locate relevant files based on the domain and issue description:
src/entities/lecture/model/useEnrollLecture.ts, src/app/lectures/[lectureId]/page.tsxsrc/components/common/LectureCard.tsxsrc/stores/authStore.ts, src/shared/lib/axios.tssrc/entities/notice/, src/app/notification/Read the identified files to understand the current implementation before proposing a plan.
## Issue #{N}: {title}
**Type:** {bug | feature | design | chore}
**Domain:** {lecture | notice | auth | component | infra}
**Affected layers:** {entities | components | pages | shared}
### Summary
{1-2 sentences on what the issue is about}
### Root cause / Gap
{For bugs: what is causing it. For features: what is currently missing.}
### Work plan
1. [{layer}] {specific action} — {file path}
2. [{layer}] {specific action} — {file path}
...
### Suggested commit type
`{type}`: {short description}
### Notes
{Any edge cases, risks, or questions to clarify before starting}
After outputting the plan, ask:
"Should I start implementing this now with the rels-orchestrator?"
If yes, hand the work plan to rels-orchestrator as the requirements input.
gh issue view {N} --json closedByPullRequests