Automated Deployment

VerifiedCaution

Automates application deployment to specified environments (production, staging, QA) with pre-checks including Git status, correct branch, tests, and environment variables. Supports multiple project types (FastAPI on VPS, Next.js on Vercel, Docker, AWS Lambda) and includes automatic rollback on failure.

Sby Skills Guide Bot
DevOpsIntermediate
6/2/2026
Claude Code
#deployment#rollback#environment#pre-deployment-checks#health-check

Recommended for

Automated summary

Deploys an application to a specified environment with pre-deployment checks, health validation, and automatic rollback on failure.

Strengths

  • Pre-deployment checks (git status, branch, tests, environment variables)
  • Automated rollback procedure on failure
  • Supports multiple project types (FastAPI, Next.js, Docker, AWS Lambda)

Limitations

  • Deployment commands are specific to projects listed in the skill
  • Requires existing .env files and configuration
  • Does not handle initial setup or infrastructure provisioning
When to use it

Use this skill for repeatable, verified deployments with rollback capability in well-known environments.

When not to use it

Avoid using for first-time deployments, infrastructure setup, or undocumented environments.

Security analysis

Caution
Quality score90/100

The skill automates legitimate deployment tasks with pre-checks and rollback, using powerful system tools. It is designed for operational use and carries inherent risk if executed in untested or unauthorized environments, but contains no malicious instructions.

Findings
  • •The skill executes bash commands including ssh, systemctl, docker-compose, and curl, which could alter production infrastructure. No destructive or obfuscated payloads are present, but misuse could cause outages or data loss.
  • •Hardcoded server paths and service names may lead to unintended modifications if applied in the wrong context.
How this analysis is made

Examples

Deploy to staging
Deploy the current project to the staging environment with pre-checks and health validation.
Production deployment with rollback
Deploy to production with full pre-deployment checklist and enable auto-rollback on health check failure.

name: deploy description: Deploy application to specified environment with pre-checks and rollback capability. Use for production deployments, staging updates, or release management. argument-hint: [environment] disable-model-invocation: true allowed-tools: Bash, Read, Glob, Grep

Automated Deployment

Deploy applications with pre-deployment checks, health validation, and automatic rollback on failure.

Arguments

  • $0: Environment - production, staging, qa, development (required)

Pre-Deployment Checklist

Before deploying, verify:

  1. Git Status Clean

    git status --porcelain
    # Must be empty or only untracked files
    
  2. On Correct Branch

    • production: main or master
    • staging: staging or DEVELOPMENT
    • qa: qa or DEVELOPMENT
  3. Tests Pass

    # Run test suite first
    /test all
    
  4. Environment Variables

    • Check .env.$ENVIRONMENT exists
    • Validate required variables are set

Deployment Strategies by Project

FastAPI Projects (IONOS VPS)

eruditiontx-services-mvp, mathmatterstx-services:

# 1. Connect to server
ssh user@server

# 2. Pull latest code
cd /path/to/project
git pull origin $BRANCH

# 3. Install dependencies
uv sync

# 4. Run migrations (if any)
uv run alembic upgrade head

# 5. Restart service
sudo systemctl restart erudition-service

# 6. Health check
curl -f http://localhost:8000/health || exit 1

# 7. Verify logs
journalctl -u erudition-service -n 20 --no-pager

Next.js Projects (Vercel)

bocs-turbo apps, naiomi-frontend:

# Using Vercel CLI
vercel --prod
# or for preview
vercel

Docker Projects

agila-tax-management:

# 1. Build new image
docker-compose -f docker-compose.$ENV.yml build

# 2. Stop old containers
docker-compose -f docker-compose.$ENV.yml down

# 3. Start new containers
docker-compose -f docker-compose.$ENV.yml up -d

# 4. Health check
docker-compose -f docker-compose.$ENV.yml ps
curl -f http://localhost:PORT/health

AWS Lambda (Serverless)

bocs-serverless:

cd bocs-serverless
./deployment.sh $ENVIRONMENT

Rollback Procedure

If deployment fails:

  1. Git Rollback

    git checkout $PREVIOUS_COMMIT
    
  2. Restart Services

    sudo systemctl restart $SERVICE
    # or
    docker-compose -f docker-compose.$ENV.yml up -d
    
  3. Verify Rollback

    curl -f http://localhost:PORT/health
    

Post-Deployment

  1. Verify Health Endpoints

    curl http://localhost:PORT/health
    curl http://localhost:PORT/v1/health
    
  2. Check Logs for Errors

    journalctl -u $SERVICE -n 50 --no-pager | grep -i error
    # or
    docker logs $CONTAINER --tail 50
    
  3. Send Notification (if configured)

    • Slack webhook
    • Email notification

Output Format

Deployment: [project-name]
Environment: [production/staging/qa]
Branch: [branch-name]
Commit: [short-hash]

Pre-checks:
  Git status: CLEAN
  Branch: CORRECT
  Tests: PASSED
  Env vars: VALIDATED

Deploying...
[Deployment output]

Post-deployment:
  Health check: PASSED
  Service status: RUNNING

Deployment completed successfully!
URL: [deployed-url]

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/automated-deployment-mmio70tg/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/automated-deployment-mmio70tg' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/automated-deployment-mmio70tg/download' --output '.skill-downloads/automated-deployment-mmio70tg/SKILL.md.part' && mv '.skill-downloads/automated-deployment-mmio70tg/SKILL.md.part' '.skill-downloads/automated-deployment-mmio70tg/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

Tools declared by the author (check availability in your agent): Bash, Read, Glob, Grep

No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.

Claude Code
test -f '.skill-downloads/automated-deployment-mmio70tg/SKILL.md' && test -s '.skill-downloads/automated-deployment-mmio70tg/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/deploy' && cp -R '.skill-downloads/automated-deployment-mmio70tg' '.claude/skills/deploy'

OpenSkills

OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.

Official OpenSkills installation
openskills install './.skill-downloads/automated-deployment-mmio70tg'

openskills read 'automated-deployment-mmio70tg'

Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.

For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.

openskills sync

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/automated-deployment-mmio70tg/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.

Related skills