From product-shipper
Executes a full feature shipping workflow: verifies readiness, deploys to staging then production, runs post-deployment checks, and announces release. Enforces tests/code review gates and rollback plans.
How this command is triggered — by the user, by Claude, or both
Slash command
/product-shipper:shipThe summary Claude sees in its command listing — used to decide when to auto-load this command
Execute a complete feature shipping workflow from code to production deployment. ## Steps 1. Verify the feature is ready to ship: 2. Prepare the release: 3. Run pre-deployment checks: 4. Deploy to staging: 5. Deploy to production: 6. Post-deployment verification: 7. Announce the release to stakeholders. ## Format ## Rules - Never ship without passing tests and code review. - Always deploy to staging before production. - Have a documented rollback plan before deploying.
Execute a complete feature shipping workflow from code to production deployment.
Feature: <name>
Version: <version>
Deployment:
Staging: <status>
6plugins reuse this command
First indexed Mar 30, 2026
npx claudepluginhub smarks26/awesome-claude-code-toolkit --plugin product-shipper/shipExecutes a full feature shipping workflow: verifies readiness, deploys to staging then production, runs post-deployment checks, and announces release. Enforces tests/code review gates and rollback plans.
/shipDrives a change from idea to production through the OntoShip dev-flow gated pipeline, including research, spec, implementation, testing, independent review, and deployment.
/shipPrepares a release (changelog, version, release notes) and executes a deploy with rollback plan. Enforces quality gates (security, performance, testing) before publication.
/release-readinessRuns a pre-ship readiness checklist covering feature flags, rollout strategy, rollback plan, documentation, monitoring, analytics, and deployment dependencies. Consolidates api-docs, tracking-plan, and security-check status into one gate.
/shipperRuns tests, generates a changelog, bumps the version, and creates a pull request to ship working code. Accepts arguments to trigger specific ship, release, or deploy steps.
/deployPlans and documents a safe deployment strategy with feature flag lifecycle, progressive rollout stages, and pipeline safety checks. Outputs rollout-plan.md and pipeline-config.md.