autoresearch:ship

EXECUTE IMMEDIATELY.

Parse Arguments

Extract from $ARGUMENTS:

• Target: or --target — what to ship (path, PR, artifact, deployment)
• --type <type> — override auto-detection: code-pr, code-release, deployment, content, docs, package, config
• --dry-run — validate everything but don't ship
• --auto — auto-approve if no errors found
• --force — skip non-critical items (blockers still enforced)
• --rollback — undo last ship action
• --monitor N — post-ship monitoring for N minutes
• --checklist-only — only generate checklist, don't execute
• --chain, --<subcommand>

Remaining text = description of what to ship.

Setup (if Target or Type unclear)

1. Auto-detect ship type from context:
   • Has uncommitted changes or PR → code-pr
   • Has version bump / changelog → code-release
   • Has Dockerfile / deploy config → deployment
   • Has markdown / content files → content
   • Has package.json version change → package
2. If still unclear → AskUserQuestion (single batch): Q1 (What): "What are you shipping?" — code PR, release, deployment, content, docs, package Q2 (Target): "Specific target?" — current branch, specific PR, specific path Q3 (Mode): "How to ship?" — full workflow, dry-run only, checklist only If all clear → skip.

Phase 1: Identify

• Determine ship type (auto-detected or --type override)
• Identify target artifact(s)
• Map to domain-specific checklist

Phase 2: Inventory

Gather everything that will be shipped:

• Files changed (git diff)
• Dependencies affected
• Config changes
• Migration files
• Breaking changes

Phase 3: Checklist

Generate domain-specific checklist:

Code PR: tests pass, types check, lint clean, no secrets, PR description, reviewers assigned Release: version bumped, changelog updated, migration tested, rollback plan Deployment: env vars set, health checks configured, rollback ready, monitoring active Content: links valid, images optimized, SEO metadata, spell check Package: version bumped, README updated, breaking changes documented, CI green