메뉴
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 통과 확인".
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
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.
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.
| name | verify-loop |
| description | 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 통과 확인". |
Mirror .github/workflows/flutter-ci.yaml locally and iterate until green.
.fvmrc) — prefix every Flutter/Dart command with fvm so the pinned version is used. Run fvm install after clone..env.dev / .env.prod must exist (gitignored). If missing, copy .env.example to both names — otherwise analyze fails with asset_does_not_exist.fvm flutter pub get if dependencies changed.Repeat until all steps pass (max 5 iterations, then stop and report what's still failing):
fvm dart run build_runner build --delete-conflicting-outputs
fvm flutter analyze --no-fatal-infos
test/ contains *_test.dart files):
fvm flutter test
// ignore or delete tests to pass), then re-run from the failed step.Appium UI tests are not part of the local loop — CI runs them on an emulator (
.github/workflows/appium-ui.yml) for every PR touchinglib/,integration_test/,appium/, orpubspec.yaml. Run the suite locally (cd appium && npm test) only to reproduce a CI failure.
analysis_options.yaml or skipping tests requires explicit user approval.