// Dallyrun Backend 의 Conventional Commits 규칙과 PR 템플릿에 맞춰 gh CLI 로 Pull Request 를 생성합니다. PR 생성, `gh pr create`, 이슈 해결 후 PR 단계에서 사용합니다.
[HINT] Download the complete skill directory including SKILL.md and all related files
| name | create-pr |
| description | Dallyrun Backend 의 Conventional Commits 규칙과 PR 템플릿에 맞춰 gh CLI 로 Pull Request 를 생성합니다. PR 생성, `gh pr create`, 이슈 해결 후 PR 단계에서 사용합니다. |
Dallyrun Backend 의 컨벤션에 맞는 형식으로 PR을 생성합니다.
형식:
<type>(<scope>): <subject>
feat, fix, refactor, chore, docs, test, style, perf, build, ciauth, member, running, share, docs, ci 등)예시:
feat(share): 러닝 세션 공유 링크 만료 시간 커스터마이징fix(auth): 로그아웃 인증 규칙 수정docs(api): refresh 엔드포인트 명세 추가.github/pull_request_template.md 를 단일 출처로 따른다.
git status, git diff main...HEAD, git log main..HEAD --oneline 으로 변경 범위를 확인한다.main 이면 중단하고 feature 브랜치 생성을 사용자와 확인한다.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, and inline review threads.
- 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`, and latest comments.
- Query PR/issue-level reactions as well as review and comment reactions. The bot `+1` reaction can appear on the PR itself; `gh api repos/<owner>/<repo>/issues/<number>/reactions` must be checked.
- CI success plus a `content == "+1"` reaction from chatgpt-codex-connector[bot] created after the latest PR commit is the pass condition.
- Other reactions such as `-1`, `eyes`, `heart`, or `rocket` are not pass signals.
2. Focus on actionable comments from chatgpt-codex-connector[bot], but also respect human requested changes.
3. Continue this cycle until all actionable review comments are resolved, including new comments posted after previous fixes.
4. 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.
5. If the PR is merged or closed, report the final state and delete this automation.
6. 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
7. 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
8. If there are no unresolved actionable review comments, no human requested changes, CI build/check passed, chatgpt-codex-connector[bot] left a `content == "+1"` reaction on the PR/issue, review, or comment after the latest PR commit, and the PR is mergeable:
- do not merge while the bot `+1` reaction is missing or older than the latest commit, even if review threads are empty
- confirm the completion sequence: reviews resolved -> CI passed -> bot `+1` reaction confirmed -> PR mergeable
- 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, missing or stale chatgpt-codex-connector[bot] `+1` reaction, unresolved actionable reviews, human requested changes, or a dirty unrelated worktree.
All GitHub Pull Request review comments must be written in Korean.
main 브랜치에 직접 커밋하거나 push하지 않는다.--no-verify와 force push를 사용하지 않는다.