メニュー
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 반영".
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
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.
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.
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-pr-review |
| description | 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 반영". |
If a PR number is given, use it. Otherwise, detect from the current branch:
gh pr view --json number,title,url
# Inline code review comments (line-level)
gh api repos/:owner/:repo/pulls/{PR_NUMBER}/comments \
--jq '[.[] | {id, path, line, body, user: .user.login}]'
# General review-level comments
gh pr view {PR_NUMBER} --json reviews \
--jq '.reviews[] | select(.state != "APPROVED") | {id, body, state, author: .author.login}'
Get owner/repo from:
gh repo view --json owner,name --jq '"\(.owner.login)/\(.name)"'
For every review comment, in order:
Group comments on the same file to minimize reads.
npx tsc --noEmit
Fix any type errors before proceeding.
Group review comments by what they change. Commit each group separately — same rule as rels-git-commit. Record the hash of each commit to use in the reply.
git add {files for this change}
git commit -m "{type}: {한국어 설명}"
git rev-parse --short HEAD # save this hash for the reply
Examples of how to split commits:
fix: Spinner를 인라인 JSX로 교체fix: 동적 라우트 파라미터명 수정fix: gh api 경로 플레이스홀더 수정After all commits, push once:
git push
Reply to each comment with the hash of the specific commit that fixed it:
gh api repos/VOID-GSM/Rels-front/pulls/{PR_NUMBER}/comments/{COMMENT_ID}/replies \
-X POST \
-f body="반영했습니다. {HASH_OF_THIS_FIX}"
Reply format — commit hash only, no description:
반영했습니다. a3f91bc
If the comment is a question (no code change needed), reply with a brief explanation in Korean.
If disagreeing or needing clarification:
확인했습니다. 의도한 동작이 맞다면 유지하겠습니다. 의견 주시면 반영하겠습니다.
## 리뷰 반영 결과
커밋: {SHORT_HASH}
반영 완료 {N}건:
1. {file}:{line} → 답글 게시 ✓
2. {file}:{line} → 답글 게시 ✓
건너뜀 (질문/확인 필요): {해당 항목}