mcpField
D
deploy

deploy

github.com/shipshitdevCloud & DevOps3898 installsUpdated today
Repository

About deploy

Deploy is a skill that guides agents in deploying a web app from trunk to preview, staging, or production. It requires quality gates and post-deploy verification, provides a rollback path, and requires explicit confirmation before production deployments.

Key features

  1. 01Run formatting, lint, type-check, and other pre-deploy gates
  2. 02Deploy from trunk to staging or production
  3. 03Check health, logs, and critical flows
  4. 04Provide rollback steps for failures
  5. 05Require explicit confirmation before production

Use cases

  1. 01Deploy trunk changes to staging
  2. 02Verify a production deployment and critical user flows
  3. 03Recover and redeploy after a failed deployment

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/shipshitdev/skills --skill deploy

After installing, type/deployin Claude Code to confirm it loaded.

Bundled filesreferences/workflow.md

Details

From the project README

Deploy

Deploy a web app from the trunk to staging or production with gates, verification and a rollback path.

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 or tags only through the release skill

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:

  • Run a delegate by reading its playbook under the installed skills directory and following it (/<router> <action>: <router>/references/<action>.md; /<name>: <name>/SKILL.md); skills here are user-invoked only, so the Skill tool cannot load them.
  • release for gating the trunk SHA and cutting the release
  • /git ci for failed GitHub Actions checks

Local quality gates (mandatory)

Before every deployment, run the repository's own format, lint and type-check scripts (plus tests and build when configured). Resolve the real script names from package.json; never guess or chain package managers (use the repo's own, Bun by default). Fix failures before pushing or deploying. Prefer CI-driven deploys over running provider CLIs locally.

Process

Staging
  1. Ensure trunk CI is green.
  2. Trigger the staging deploy from the trunk (no staging branch).
  3. Wait for CI and staging health checks to pass.
Production
  1. Ensure staging is healthy.
  2. Require explicit confirmation. Production is critical.
  3. Deploy to production from the trunk.
  4. Monitor the deployment; watch health endpoints and error tracking for 15 minutes.
Hotfix

Branch hotfix/xxx off the trunk (default branch), fix, PR to trunk, merge, deploy to production.

Post-deploy verification

  1. Check health endpoints.
  2. Check error tracking (Sentry or similar).
  3. Verify critical user flows.
  4. Check deployment logs.

Rollback

If the deployment fails, revert the merge commit and redeploy.

References

references/workflow.md has platform-specific deployment details, AWS patterns, CI/CD integration and rollback procedures. Its command examples are generic placeholders; substitute the repo's own package manager and scripts.

Comments

Markdown supported