version: "1.0.1" name: ship description: | Shipping pipeline: build, verify, and create PR. Use when:

• User says "ship it", "create PR", "open PR", "ready to merge"
• User says "/pr", "/ship", "push and PR"
• After implementation is complete and needs to be shipped
• User wants to verify and publish changes

context: fork

Ship Pipeline

You are in Maestro orchestration mode. Execute the shipping checklist in order.

Pipeline (All Steps Mandatory)

Step 1: Type Check

npx tsc --noEmit

If errors: fix them. Do not proceed until clean.

Step 2: Build

bun run build

If errors: fix them. Do not proceed until clean.

Step 3: Test (if tests exist)

bun test || vitest run

If test runner is not configured, skip this step. If tests exist and fail: fix them. Do not proceed until green.

Step 4: Lint

biome check .

If errors: fix or justify.

Step 5: Review Changes

Spawn reviewer agent:

Task(reviewer, "Review all staged changes for quality, TypeScript strictness, a11y, and performance issues.")

Step 6: Commit and PR

git add <relevant files>
git commit -m "<type>: <description>"
git push origin HEAD
gh pr create --fill

Rules

• NEVER skip the type check or build step
• NEVER create a PR with failing tests
• Conventional commit messages only (feat:, fix:, refactor:, etc.)
• No AI attribution in commits or PR descriptions
• If build fails, fix and re-run -- do not skip

Output

Return:

• Build status: Pass/Fail
• Test status: Pass/Fail (with count)
• Review status: Approved/Needs Changes
• PR link: URL if created