メニュー
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.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
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", "머지 준비".
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.
SOC 職業分類に基づく
| name | full-loop |
| description | 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. |
One issue, end to end: branch → implementation → verified commits → PR.
{type}/{N}-{slug} off fresh develop, label the issue in progress.lib/feature/{domain}/...); create the task list. If the issue is ambiguous on scope or design, ask before implementing, not after.🔀 :: (#{N}) - 제목, Korean template body, base develop), set the issue to Reviewing.♻️ :: 코드 리뷰 반영 — ... on the same branch (only when the user asks to address review comments).