← ClaudeAtlas

deploylisted

Push the task branch, open a Korean pull request, then hand off to flow:code-review for the multi-LLM review pipeline. Use this whenever development for a flow task is done and the branch is ready for review. Even when the user says "just open a PR", run the full flow — multi-LLM review is the point of this skill, not optional dressing. Run in its own session from develop; do not bundle.
gitgitWi/council-flow · ★ 1 · DevOps & Infrastructure · score 53
Install: claude install-skill gitgitWi/council-flow
# flow:deploy — Push + open Korean PR + delegate to code-review Deploy is the closing skill. It is intentionally separate from develop so reviewer LLMs see a clean diff without develop's intermediate state in context. The review pipeline itself lives in `flow:code-review`, which deploy invokes after opening the PR. Splitting the two means the review skill is reusable for arbitrary existing PRs (not just ones deploy just created). ## 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 유닛/통합 테스트 - [ ] Playwright E2E (해당 시) - [ ] 수동 확인: <어떤 시나리오를 어떻게 확인했는지> ## 스크린샷 / 영상 (UI 변경이 있는 경우) ## 관련 링크 - 플랜: `.planning/<date>-<task>/plan.md` - 리뷰 요약: `.planning/<date>-<task>/artifacts/code-review-summary.md` (자동 생성 예정) ``` Create with HEREDOC for correct formatting: ```bash gh pr cre