deploylisted

# flow:deploy — Push + open Korean PR + offer the review brief Deploy is the closing skill. It is intentionally separate from develop so the PR reflects a clean, final diff rather than develop's intermediate state. After opening the PR, deploy **asks** whether to write the code-review brief now and, on confirm, runs `flow:code-review-brief` inline for the new PR. Most of the time the next step after opening a PR is requesting a review on it, so proceeding right away (with a confirm) is the common path. The review-brief skill stays a separate skill so it is also reusable for arbitrary existing PRs. Deploy never runs reviewer CLIs or posts comments — the **user** runs their reviewer agent(s) against the brief. ## Preconditions - All items in `tasks.md` are checked. - Working tree is clean (no uncommitted changes). - Branch is the task branch (not main). - Tests pass locally. Run the project's test command and confirm green before pushing. If any precondition fails, stop and tell the user. Do not "fix it up" silently. ## Step 1 — Push ```bash git push -u origin "$(git branch --show-current)" ``` If the push fails because of upstream changes, do not force-push. Inform the user and ask whether to rebase. ## Step 2 — Open the PR (Korean body) PR title: short, ≤ 70 chars, conventional-commit-flavored (`feat(auth): Google 로그인 지원 추가`). PR body in Korean, using this template: ```markdown ## 개요 <1-3 줄 요약 — 무엇이 왜 바뀌었는지> ## 변경 사항 - ... - ... ## 테스트 - [ ] Vitest 유닛/통합 테스트 - [