ship
Deploy and launch a feature or product. Runs a quality gate, pre-launch checklist, and executes deployment. Use when the user is ready to ship.
What this skill does
# Ship: $ARGUMENTS You are coordinating a launch for the CEO. Time to ship. ## Step 1: Final Quality Gate Delegate to `@qa` with the project's entry point and test commands. Task: final pre-ship quality gate — run test suites, scan for security vulnerabilities, check for hardcoded secrets or debug artifacts. Report findings using severity format (Critical/Warning/Suggestion/Positive). If any Critical findings, the ship is blocked — STOP and present them to the CEO before proceeding. ## Step 2: Pre-Launch Checklist Generate a checklist tailored to the project: - [ ] All tests passing - [ ] Environment variables configured for production - [ ] Database migrations ready (if applicable) - [ ] API keys and secrets secured (not hardcoded) - [ ] Error monitoring configured (Sentry, etc.) - [ ] README/docs updated - [ ] Git changes committed and pushed Present the checklist to the CEO. Walk through each item — check off what's already done, flag what needs attention. Proceed on approval. ## Step 3: Deploy Read `.solopreneur/preferences.yaml` for the deployment strategy. ### If deployment is configured (`deployment.configured: true`): Execute deployment based on the platform: **Vercel**: - If Vercel MCP tools are available (`mcp__claude_ai_Vercel__deploy_to_vercel`), use them directly - Otherwise, run `vercel --prod` via CLI - After deployment, verify: check build logs for errors, confirm the deployment URL is reachable **Netlify**: - Run `netlify deploy --prod` via CLI - Verify the deployment URL is reachable **GitHub Pages**: - Push to the configured branch (typically `gh-pages` or `main`) - Verify the pages URL is reachable **Other/Custom**: - Read `deployment.notes` from preferences for platform-specific instructions - Delegate to `@engineer` to execute the deployment steps **For all platforms:** - Report the live URL to the CEO (ephemeral — shown in conversation, not saved to a file) - If deployment fails, show the error and offer to troubleshoot with the `@engineer` - If `deployment.rollback` is not yet in preferences, generate platform-specific rollback instructions and save them ### If deployment is deferred (`deployment.configured: false` or `deployment.platform: none`): Ask the CEO: > Your code is ready to go, but we haven't set up deployment yet. > Want to set that up now? I can help you pick a platform and get it running. If yes, follow the same deployment setup flow as `/build` Step 1.75 (ask platform, configure, deploy). Save to preferences. If no, skip deployment — just ensure git changes are committed and pushed. ### If no deployment config exists at all: Same as the deferred case above. This handles legacy projects or situations where `/build` wasn't used. ## Step 4: Post-Deploy Verification If deployment was executed: 1. Wait briefly for the deployment to propagate 2. Check the live URL is responding (delegate to `@qa` if browser tools are available) 3. Report status to the CEO (all ephemeral — shown in conversation, not saved to files): - Deployment URL - Build status (success/failure) - Any warnings from the build logs - Rollback instructions (also saved in preferences.yaml for future reference) ## Step 5: Next Steps End with the next step prompt: ``` -> Next: Announce the launch: /solopreneur:release-notes "customers" /solopreneur:release-notes "social media" ```
Related in Cloud & DevOps
appbuilder-action-scaffolder
IncludedCreate, implement, deploy, and debug Adobe Runtime actions with consistent layout, validation, and error handling. Use this skill whenever the user needs to add actions to an App Builder project, understand action structure (params, response format, web/raw actions), configure actions in the manifest, use App Builder SDKs (State, Files, Events, database), deploy and invoke actions via CLI, debug action issues, or implement patterns such as webhook receivers, custom event providers, journaling consumers, large payload redirects, action sequence pipelines, and Asset Compute workers. Also trigger when users mention serverless functions in Adobe context, action logging, IMS authentication for actions, or cron-style scheduled actions.
orchestrating-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. Use this skill when the user needs a multi-step Data Cloud pipeline, cross-phase troubleshooting, or data space and data kit management. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase sf data360 workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching phase-specific skill), the task is STDM/session tracing/parquet telemetry (use observing-agentforce), standard CRM SOQL (use querying-soql), or Apex implementation (use generating-apex).
github-project-automation
IncludedAutomate GitHub repository setup with CI/CD workflows, issue templates, Dependabot, and CodeQL security scanning. Includes 12 production-tested workflows and prevents 18 errors: YAML syntax, action pinning, and configuration. Use when: setting up GitHub Actions CI/CD, creating issue/PR templates, enabling Dependabot or CodeQL scanning, deploying to Cloudflare Workers, implementing matrix testing, or troubleshooting YAML indentation, action version pinning, secrets syntax, runner versions, or CodeQL configuration. Keywords: github actions, github workflow, ci/cd, issue templates, pull request templates, dependabot, codeql, security scanning, yaml syntax, github automation, repository setup, workflow templates, github actions matrix, secrets management, branch protection, codeowners, github projects, continuous integration, continuous deployment, workflow syntax error, action version pinning, runner version, github context, yaml indentation error
sf-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase `sf data360` workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching sf-datacloud-* skill), the task is STDM/session tracing/parquet telemetry (use sf-ai-agentforce-observability), standard CRM SOQL (use sf-soql), or Apex implementation (use sf-apex).
fabric-cli
IncludedUse this skill for Fabric.so CLI workflows with the `fabric` terminal command: diagnose/install/login, search or browse a Fabric library, save notes/links/files, create folders, ask the Fabric AI assistant, manage tasks/workspaces, generate shell completion, check subscription usage, produce JSON output, and use Fabric as persistent agent memory. Do not use for Microsoft Fabric/Azure/Power BI `fab`, Daniel Miessler's Fabric framework, Python Fabric SSH, Fabric.js, or textile/fashion fabric.
lark
IncludedLark/Feishu CLI skills: lark-cli operations for docs, markdown, sheets, base, calendar, im, mail, task, okr, drive, wiki, slides, whiteboard, apps, approval, attendance, contact, vc, minutes, event. Use when the user needs to operate Lark/Feishu resources via lark-cli, send messages, manage documents, spreadsheets, calendars, tasks, OKRs, deploy web pages, or any Feishu/Lark workspace operations.