/deploy

> Build, validate, and deploy to target environment.

170 stars

byMiosa-osa

View on GitHub Installation ↓

Best use case

/deploy is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

> Build, validate, and deploy to target environment.

Teams using /deploy should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

You only need a quick one-off answer and do not need a reusable workflow.
You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/deploy/SKILL.md --create-dirs "https://raw.githubusercontent.com/Miosa-osa/canopy/main/library/skills/development/deploy/SKILL.md"

Manual Installation

Download SKILL.md from GitHub
Place it in .claude/skills/deploy/SKILL.md inside your project
Restart your AI agent — it will auto-discover the skill

How /deploy Compares

Feature / Agent	/deploy	Standard Approach
Platform Support	Not specified	Limited / Varies
Context Awareness	High	Baseline
Installation Complexity	Unknown	N/A

Frequently Asked Questions

What does this skill do?

> Build, validate, and deploy to target environment.

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

SKILL.md Source

# /deploy

> Build, validate, and deploy to target environment.

## Usage
```
/deploy <environment> [--dry-run] [--skip-tests] [--rollback]
```

## What It Does
Orchestrates the full deployment pipeline: build, test, validate, push, and verify. Supports staging and production environments with appropriate safeguards. Dry-run mode shows what would happen without executing.

## Implementation
1. **Pre-flight checks** -- verify branch, clean working tree, all tests pass.
2. **Build** -- compile for target environment with production optimizations.
3. **Validate** -- run smoke tests against the build artifact.
4. **Deploy** -- push to target (Docker registry, Fly.io, AWS, etc.).
5. **Health check** -- verify the deployment is healthy (HTTP checks, log monitoring).
6. **Rollback** (if `--rollback` or health check fails) -- revert to previous version.

## Examples
```bash
# Deploy to staging
/deploy staging

# Dry run to see what would happen
/deploy production --dry-run

# Rollback production to previous version
/deploy production --rollback

# Skip tests (use with caution)
/deploy staging --skip-tests
```

## Command