القائمة
Pre-deploy gate: typecheck (must exit 0) -> full test suite (all pass) -> build. Any red = stop and report which gate failed. Green = print the deploy command, never run it.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Route a task to the least intrusive executive-function support based on the user's stated current capacity, memory load, activation, and motivation. Use when work feels stuck, overwhelming, hard to hold in mind, or when the user asks for neurodivergent-friendly support without wanting a diagnostic or coaching ritual.
Reduce work to the smallest safe and useful outcome when capacity is low or burnout is present. Use when the user explicitly says they are depleted, overwhelmed, unable to start, or asks for the minimum viable version of a task.
Create a truthful activation bridge for a task that has low urgency, novelty, interest, challenge, or immediate feedback. Use when the user says they are stuck or avoiding a known task despite understanding it.
Reduce language, sensory, and uncertainty load while preserving complete information. Use when the user requests direct or scannable communication, has low capacity, is navigating a new flow, or needs explicit expectations and examples.
Turn a vague, oversized, or initiation-resistant outcome into an executable sequence with a visible first action and definition of done. Use when dependencies are hidden, the task spans multiple systems, or the user cannot identify where to begin.
Externalize time, checkpoints, stopping rules, and context transitions. Use when estimates are uncertain, a task may expand indefinitely, the user is switching topics, or an interruption risks losing the current state.
| name | ship-preflight |
| description | Pre-deploy gate: typecheck (must exit 0) -> full test suite (all pass) -> build. Any red = stop and report which gate failed. Green = print the deploy command, never run it. |
| created | "2026-06-07T00:00:00.000Z" |
| updated | "2026-06-07T00:00:00.000Z" |
| tags | ["deploy","ship","preflight","gate","tests","typecheck","build","release","safety"] |
| triggers | [{"event":"PreToolUse","match":"git_push"}] |
A blocking gate before any deploy / notarize / release — mined from your own most-repeated rule ("typecheck exit 0; tests ALL pass; then build"). Deploy/ship is your widest theme; make the gate one command that refuses to pass on red.
Before any deploy, notarize, publish, or release. Run it as the first step of a ship flow, or schedule it pre-deploy.
shell_cmd (e.g. tsc --noEmit, cargo check). Must exit 0.Run in order; capture each gate's result.
Deploy, publish, notarize, or push a release tag automatically. The kernel gates these; the preflight stops at "ready — here's the command".
vanta run "ship preflight for <project>: typecheck (exit 0) -> full tests (all pass) -> build; green prints the deploy command, never runs it".Mined from your own repeated ship gate (build-catalog §9), aligned with Boris Cherny's verification-as-bottleneck frame (14:37). Solo-oriented: prove readiness, the human ships.