Menu
Review changes, open PRs, run pre-launch checks, staged rollouts, and rollback. Use when preparing to ship to production or closing out a branch.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Build a personalized learning roadmap with milestones and practice checkpoints
Structured document review for structure, clarity, and technical accuracy. Use for "review this doc", feedback, critique, or /doc-review.
Render a documentation-style Cursor Canvas that organizes architecture notes, API references, walkthroughs, and how-tos into a navigable layout with sections, tables of contents, and cross-references. Use when the user asks for a docs canvas, documentation overview, architecture walkthrough, API reference page, or wants to render structured documentation as an interactive canvas.
Conductor/subagent routing for tasks across multiple harnesses. Assesses task complexity and intent, then dispatches to the appropriate subagent model via a harness-specific adapter. Supports Anthropic (Claude), Cursor, OpenCode, Codex (OpenAI), and Pi adapters. Use via /dynamic-task command or direct invocation from other skills.
Agent evaluation framework. Measure agent performance, identify weaknesses, and track improvement over time. Use when assessing agent quality, comparing approaches, or validating changes.
Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when the user wants to stress-test a plan, get grilled on their design, or mentions "grill me".
| name | shipping-and-launch |
| description | Review changes, open PRs, run pre-launch checks, staged rollouts, and rollback. Use when preparing to ship to production or closing out a branch. |
| metadata | {"category":"user-invoked"} |
| disable-model-invocation | true |
Default output: return only the result, blockers, and required evidence. Omit preambles, process narration, repeated context, confidence scores, and follow-up offers. Use at most five bullets unless a required artifact or schema needs more.
Shipping is review โ PR โ checklist โ staged rollout โ monitor. Small, frequent releases beat large batches. Do not skip review because launch checklists exist, and do not ship because staging looked fine without production safeguards.
Gather context: diff against base branch, uncommitted changes, recent commits, changed files, and user intent from recent chats if useful.
git fetch origin main
git diff origin/main...HEAD
git status
gh pr checks --json name,bucket,state,workflow,link
Then:
Prioritize correctness, security, and regressions over style-only comments. Fix pre-commit failures; never bypass hooks. Use gh pr checks as the source of truth for PR readiness.
Output: findings (critical / warning / note), tests run, PR URL.
Code quality: tests pass, review approved, no critical/high issues, coverage meets threshold.
Security: no secrets in code/config, dependency audit clean, inputs validated, auth tested.
Performance: baseline established, no CWV/regression, no N+1, load tested if throughput-sensitive.
Operational: feature flag ready, monitoring configured, rollback tested, staging verified.
Automatic triggers: error rate, SLO breach, health check failures.
Manual rollback: identify bad deployment โ revert to last good โ verify โ communicate โ root-cause before redeploy.
Create (off) โ develop behind flag โ test internally โ gradual rollout โ GA โ remove flag and dead code path.
| Excuse | Counter |
|---|---|
| "It works on staging, ship it" | Staging does not replicate production traffic and data. |
| "We can monitor after launch" | Monitoring must exist before launch. |
| "Rollback is too slow, fix forward" | Fix-forward under pressure adds risk. |
| "Staged rollout is too slow" | Staged rollouts beat incident response. |
| "Flag cleanup can wait" | Flags become permanent debt. Schedule cleanup now. |