ship

name	ship
description	Full pipeline — implement, verify, review, then commit and open a PR

Full pipeline: implement, verify, commit, and create a PR. Execute all steps automatically without asking between phases unless genuinely ambiguous.

Task: the task/scope the user described when invoking this skill (if none given, ask or infer from context)

Phase 1: Understand

• Scan project structure, tech stack, patterns.
• Find and read files related to the task. Synthesize findings.

Phase 2: Design (UI 작업 포함 시에만)

Skip for backend-only, bug-fix, or refactor tasks with no UI change.

• design-system/MASTER.md가 있으면 로드해 재사용 (필요 시 page override).
• 없으면 ~/.codex/skills/ui-ux-pro-max/ (reasoning-rules.md → styles.md)로 토큰 확정 후 design-system/MASTER.md 생성.
• 구현은 MASTER 토큰 100% 준수 (raw hex 금지, 시맨틱 토큰만, 이모지 구조 아이콘 금지, 터치 타겟 ≥44pt).

Phase 3: Plan

Implementation plan: files to modify, approach, risks. Identify dependency order.

Phase 4: Implement

Implement sequentially from the foundation (types → logic → UI). Follow existing conventions.

Phase 5: Verify

Run and auto-fix failures (up to 3 attempts): build, lint/type-check, tests. For UI changes also run /design-audit checks.

Phase 6: Review

Review your changes for quality (single responsibility, no duplication, clear naming, error handling, no dead code, perf, consistency) and security (no secrets, no injection, input validation, no data exposure). Fix CRITICAL/WARNING findings.

Phase 7: Git & PR

1. Stage relevant files (exclude .env, secrets, large binaries).
2. Create commit: type(scope): description.
3. If on main/master, create a new branch first.
4. Push to remote with -u.
5. Create a PR with gh pr create: clear title (<70 chars), summary of changes, test plan, review findings addressed.

Phase 8: Report

PR URL, summary of changes, review results (quality + security), manual testing needed.

Rules

• Execute autonomously — don't ask between phases.
• Auto-fix failures up to 3 attempts.
• Ask only if genuinely ambiguous.