[HINT] Download the complete skill directory including SKILL.md and all related files
| name | source-command-pr |
| description | 현재 브랜치 push + 컨벤션 맞춰 PR 생성 |
Use this skill when the user asks to run the migrated source command pr.
루트 AGENTS.md 의 Git Convention 섹션을 따라 PR을 생성한다.
git status / git diff main...HEAD / git log main..HEAD --oneline 으로 변경을 분석한다.feat / fix / refactor / chore / docs / test) 중 적절한 것을 고른다.<prefix>(<scope>): <요약> (한글 OK, 70자 이내)..github/pull_request_template.md를 단일 출처로 따른다.git push -u origin <branch> 로 push.gh pr create --base main --head <branch> --title "..." --body "$(cat <<'EOF' ... EOF)" 로 PR 생성.PR <number> review merge follow-upPR 생성 후 아래 템플릿의 <...> 값을 실제 PR 정보로 바꿔 heartbeat automation을 생성한다.
Check GitHub PR #<number> in <absolute-repo-path>.
Every run:
1. Inspect PR state, mergeability, CI checks, review comments, inline review threads, and reactions on the PR body.
- Do not rely only on flat comment views such as `gh pr comments` or `gh pr view`.
- Query GitHub GraphQL `reviewThreads` and check each thread's `isResolved`, `isOutdated`, `path`, `line`, latest comments, and comment `reactionGroups` or `reactions`.
- Use the GitHub REST Reactions API for the PR body and check for `user.login == "chatgpt-codex-connector[bot]"` and `content == "+1"`.
2. Focus on actionable comments from chatgpt-codex-connector[bot], but also respect human requested changes.
3. Treat the automated review as passed only when CI has passed and the PR body reaction list contains `user.login == "chatgpt-codex-connector[bot]"` and `content == "+1"`. Do not treat review or review-comment reactions as this pass signal.
4. Continue this cycle until all actionable review comments are resolved, including new comments posted after previous fixes.
5. Treat already resolved, outdated, or obsolete review threads as read-only context; do not re-apply the same fix unless a new unresolved thread asks for it.
6. If the PR is merged or closed, report the final state and delete this automation.
7. If there are actionable review comments that can be fixed safely:
- implement only the requested fixes
- do not modify unrelated files
- run the narrowest validation gate from .codex/docs/VALIDATION.md
- commit with a Conventional Commit message
- push to the PR branch without force push
- report Done with changed files and validation
- keep monitoring
8. If comments are informational, already addressed, non-actionable, or require product/design/API/security judgment:
- do not edit code
- report Read or Blocked with the reason
- pause/delete this automation only when human judgment is required or the PR is closed
9. If there are no unresolved actionable review comments, no human requested changes, no blocking human emoji reactions, CI build/check passed, the PR is mergeable, and the PR body reaction list contains `user.login == "chatgpt-codex-connector[bot]"` and `content == "+1"`:
- merge the PR
- delete the remote branch
- switch local repo to main
- pull latest main
- prune origin
- delete the local PR branch if present
- report Merged
- delete this automation
Never use --no-verify.
Never force push.
Never merge with pending/failed CI, unresolved actionable reviews, human requested changes, missing PR body reaction `user.login == "chatgpt-codex-connector[bot]" && content == "+1"`, blocking human emoji reactions, or a dirty unrelated worktree.
All GitHub Pull Request review comments must be written in Korean.
main 브랜치에 직접 커밋/푸시 금지.