메뉴
Pre-launch validation and release workflow. Use when the user says 'ship', 'release', 'deploy', or 'ready to merge'.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | ship |
| description | Pre-launch validation and release workflow. Use when the user says 'ship', 'release', 'deploy', or 'ready to merge'. |
Validate and ship: $ARGUMENTS
Run these checks in order. Stop at the first failure.
why-not-mechanizable: skill workflow guidance; each step requires understanding the surrounding context (repo, task shape, prior state).
/verify-done - stop on first failure (typecheck + lint + tests + build) (review-time: see section note)console.log, debugger, .only(), TODO without issue link) (review-time: see section note)git fetch origin main && git rebase origin/main (review-time: see section note)git status is clean (review-time: see section note)feat:, fix:, refactor:, etc.) (review-time: see section note)(review-time: see section note)(review-time: see section note).env, credentials, keys) (review-time: see section note)references/security-checklist.md; invoke cybersecurity-expert agent for risky changes)(review-time: see section note)npm audit with zero critical/high (review-time: see section note)(review-time: see section note)(review-time: see section note)(review-time: see section note)(review-time: see section note)(review-time: see section note)(review-time: see section note)(review-time: see section note)(review-time: see section note)(review-time: see section note)(review-time: see section note)(review-time: see section note)
fix: commits = PATCH bump (review-time: see section note)feat: commits = MINOR bump (review-time: see section note)BREAKING CHANGE: = MAJOR bump (review-time: see section note)(review-time: see section note)If all checks pass:
gh pr create - include summary, test plan, and any deployment notes (review-time: see section note)(review-time: see section note)(review-time: see section note)(review-time: see section note)If any check fails:
(review-time: see section note)(review-time: see section note)Code review focused exclusively on over-engineering. Finds what to delete: reinvented standard library, unneeded dependencies, speculative abstractions, dead flexibility. One line per finding: location, what to cut, what replaces it. Use when the user says "review for over-engineering", "is this over-engineered", or invokes /prune. Complements correctness-focused review; this one only hunts complexity.
Implement code incrementally with quality gates. Use when the user says 'build', 'implement', or when starting the implementation phase of an approved plan.
Grilling session that challenges your plan against the existing domain model, sharpens terminology, and updates documentation (CONTEXT.md, ADRs) inline as decisions crystallise. Use when user wants to stress-test a plan against their project's language and documented decisions.
Structured production-incident investigation. Forces evidence-first hypothesis ranking before any code change. Use when given an error message, Sentry alert, failing log, or 'investigate <X>' request.
Fetch and digest Sentry issue data (issue summary, tags, stack trace, breadcrumbs, latest event) by short ID, numeric issue ID, or sentry.io URL. Org-agnostic - works for any Sentry org the local token can access. Use when the user mentions a Sentry issue or short ID (e.g. MY-PROJECT-4X2), pastes a sentry.io issue URL, or asks to investigate/debug a Sentry error.
Create or update a diagram. Picks mermaid vs drawio per rules/diagrams.md, writes the source file, previews via MCP. Use when the user says 'diagram', '/diagram', or asks for a flowchart/architecture/sequence/state diagram.