/deploy

Automate software deployment to staging and production with pre-deployment checks.

3|1|Updated Feb 7, 2026
One-click install
npx skills add https://github.com/yon/agentic-dev-os --skill deploy-yon
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: /deploy
Source: https://github.com/yon/agentic-dev-os/tree/main/.claude/skills/deploy
Command: npx skills add https://github.com/yon/agentic-dev-os --skill deploy-yon

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the process of deploying your project to different environments, ensuring consistency and reducing manual errors.

Core Features & Use Cases

  • Environment Selection: Deploy to staging (default) or production.
  • Pre-Deployment Checks: Enforces mandatory checks like build, test, lint, and type checking before deployment.
  • Production Confirmation: Requires explicit user confirmation for production deployments.
  • Post-Deployment Verification: Includes steps for verifying successful deployment and rollback procedures.

Quick Start

Deploy the project to the staging environment.

Frequently Asked Questions about /deploy

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate deployment to staging and production environments?

You can automate deployment to staging and production by enforcing mandatory pre-deployment checks including build, test, lint, and type-checking. Production deployments require an additional quality score gate and explicit user confirmation before proceeding.

What pre-deployment checks are required for a CI/CD deployment pipeline?

Required pre-deployment checks for a deployment pipeline include build, test, lint, and type-checking stages. Production deployments enforce an additional quality score gate to ensure code stability before releasing to the live environment.

Does deploying to production require manual confirmation?

Yes, deploying to production requires explicit user confirmation to prevent accidental releases. This step follows the successful completion of all pre-deployment checks and the mandatory quality score gate.

How do I verify a successful deployment and perform a rollback?

Post-deployment verification involves checking the deployed application for successful operation in the target environment. If issues are found, rollback procedures are facilitated to revert the project to its previous stable state.

Can I deploy to staging by default without targeting production?

Yes, staging is the default deployment target, allowing you to test changes safely without affecting the live environment. Selecting production requires explicit confirmation and passing a stricter quality score gate.