deploy
Run deployment workflows for web applications (staging, production). Use when user says 'deploy', 'push to staging', 'release', 'ship it', or 'go live'.
What this skill does
# Deploy Streamline deployment workflows for React, Next.js, NestJS applications to various environments. ## Contract Inputs: - Repository root - Target environment: preview, staging, or production - Optional branch, PR number, deployment provider, and health-check URL Outputs: - Pre-deploy gate results - Deployment route and provider - Verification status - Rollback or follow-up instructions when needed Creates/Modifies: - Local changes only when fixing failed gates before deployment - Release PRs only when delegated to `release-pr-gates` External Side Effects: - May trigger provider deployments - May create or update GitHub PRs through delegated release skills - May read logs and monitoring systems Confirmation Required: - Before production deploys - Before merging release PRs - Before rollback commands - Before force-pushes or history rewriting Delegates To: - `deployment-composer` for route discovery across providers - `release-pr-gates` for branch promotion PRs - `gh-fix-ci` for failed GitHub Actions checks - `ec2-backend-deployer` for EC2/Docker deployment setup ## When to Use - Deploying to staging or production - Setting up deployment pipelines - Managing environment-specific deployments ## Local Quality Gates (MANDATORY) Always run format, lint, and type-check locally before every release PR or deployment. These mirror the expected GitHub Actions gates and are cheap enough to run before pushing. Use the repository's package manager and scripts when present. Prefer existing scripts in `package.json`; fall back only when a script is missing. ```bash # 1. Format - required bun run format || npm run format || npx biome check --write . # 2. Lint - required bun run lint || npm run lint || bunx turbo lint # 3. Type-check - required bun run typecheck || bun run type-check || npm run typecheck || npm run type-check || npx tsc --noEmit # 4. Tests - run when configured npm test || bun run test --filter=[changed-package] # 5. Build - run when configured npm run build ``` If format, lint, or type-check fails, fix it before pushing, opening a release PR, or triggering deployment. Do not hand known local quality failures to GitHub Actions. ## Deployment Process ### To Staging 1. Ensure develop/main CI is green 2. Create PR to staging branch (if applicable) 3. Wait for CI to pass 4. Merge when green ### To Production 1. Ensure staging CI is green 2. Create PR to production branch 3. **Require explicit confirmation** — production is critical 4. Merge and monitor deployment 5. Watch health endpoints and error tracking for 15 minutes ### Hotfix Flow 1. Branch `hotfix/xxx` off production branch 2. Fix -> PR to production -> deploy 3. Merge hotfix back into develop ## Post-Deployment Verification 1. Check health endpoints 2. Monitor error tracking (Sentry, etc.) 3. Verify critical user flows 4. Check deployment logs ## Rollback If deployment fails, revert the merge commit and re-deploy. ## References See `references/workflow.md` for platform-specific deployment details, AWS patterns, CI/CD integration, and rollback procedures.
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.