메뉴
Finish the current branch — verify, commit remaining work with the emoji-:: convention, push, and open a PR to develop that passes the PR title check CI. Use when the user says "PR 올려", "출고", "ship", "머지 준비".
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
Start work on a GitHub issue — pick or create the issue, then create the convention branch ({type}/{issue}-{slug}) off fresh develop. Use when the user says "이슈 시작", "작업 시작", "start issue", or names an issue number to work on.
Run the CI-equivalent verification chain (build_runner codegen → flutter analyze → flutter test) and keep fixing + re-running until everything passes. Use before committing, before PRs, or when the user says "검증", "verify", "CI 통과 확인".
Iterative implement → verify → commit cycle on the current branch until the stated goal is done. No branch creation, no PR. Use when the user says "작업 루프", "work loop", or wants heads-down implementation of a defined task list.
Full autonomous cycle for one issue - start-work (issue → branch) → work-loop (implement/verify/commit) → ship (push → PR). Use when the user says "전체 루프", "full loop", "이슈 끝까지", or hands over an issue to complete end-to-end.
SOC 직업 분류 기준
| name | ship |
| description | Finish the current branch — verify, commit remaining work with the emoji-:: convention, push, and open a PR to develop that passes the PR title check CI. Use when the user says "PR 올려", "출고", "ship", "머지 준비". |
Take the current branch from "code done" to "PR open" following repo conventions.
{type}/{N}-{slug}). If it doesn't contain one, ask the user — the PR title check CI requires (#N).verify-loop skill. Do not push failing code.{emoji} :: {한국어 요약}
.env.dev/.env.prod or generated *.g.dart/*.freezed.dart files.git push -u origin {branch}.develop:
^[^ ] :: \(#[0-9]+\) - .+):
🔀 :: (#{N}) - {한국어 제목}
Before creating, propose ~3 candidate {한국어 제목} options via AskUserQuestion and let the user pick (or edit) — don't auto-name. The 🔀 :: (#{N}) - prefix is fixed; only the Korean title varies..github/PULL_REQUEST_TEMPLATE.md in Korean — 개요, Closes #{N}, 작업내용 (bulleted actual changes), 테스트 방법 (concrete steps), 스크린샷 (placeholder note if UI changed but no screenshot available), 질문사항, 체크리스트 (check only what was actually verified).gh ... --body-file - — PowerShell 5.1 encodes native-command stdin in the system codepage and mangles Hangul into ?. Write the body to a UTF-8 file first, then pass its path:
gh pr create --base develop --title "🔀 :: (#{N}) - {제목}" --body-file pr_body.md
gh pr edit --body-file and gh issue create/edit --body-file.) Use the Write tool to create the file (it writes UTF-8), then delete it after. The PR title via --title "..." is fine inline.🌟 Status: Reviewing.develop (never main).develop, merge develop in and re-verify before pushing.