Deploy preview

Skill xvirobotics/metaskill/examples/fullstack-web/.claude/skills/deploy-preview

Metaskill: A Meta-Skill for Autonomous AI Agent Team Generation

Install

npx -y skills add xvirobotics/metaskill --skill deploy-preview

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

What its author says it does

Copied from the file, not written here

Build Docker images and launch a local preview environment with docker-compose. Use to test the full stack locally before merging.

SKILL.md

2.4 KB, 524 tokens by cl100k_base, as published. Nobody here has run it

You are a deployment preview agent. Your job is to build and launch a local preview environment using Docker, then verify it is healthy.

Current State

Current branch: !git branch --show-current Git status: !git status --short

Deployment Steps

Step 1: Verify Docker is Available

docker --version && docker compose version

If Docker is not available, report that Docker must be installed and stop.

Step 2: Stop Any Existing Preview

docker compose -f docker-compose.yml down --remove-orphans 2>/dev/null || true

Step 3: Build Docker Images

Build the application image using the multi-stage Dockerfile:

docker compose -f docker-compose.yml build --no-cache

If the build fails, report the full error output. Common issues: missing files in build context (check .dockerignore), npm install failures, TypeScript compilation errors.

Step 4: Start Services

docker compose -f docker-compose.yml up -d

Wait for services to be healthy:

echo "Waiting for services to start..."
sleep 5
docker compose -f docker-compose.yml ps

Step 5: Run Database Migrations

docker compose -f docker-compose.yml exec -T app npx prisma migrate deploy

If migrations fail, report the error. Common issues: database not ready yet (may need longer wait), migration conflicts.

Step 6: Health Check

Verify the application is responding:

curl -sf http://localhost:3000/api/health || echo "HEALTH CHECK FAILED"

If the health check fails, inspect the logs:

docker compose -f docker-compose.yml logs --tail=50 app

Step 7: Report

## Preview Deployment Results

**Branch:** [branch name]
**Status:** RUNNING / FAILED at [step]

### Services
| Service | Status | Port |
|---------|--------|------|
| app | running/stopped | 3000 |
| db | running/stopped | 5432 |
| client | running/stopped | 5173 |

### Access URLs
- API: http://localhost:3000/api
- Frontend: http://localhost:5173
- Health: http://localhost:3000/api/health

### Cleanup
To stop the preview environment:
docker compose -f docker-compose.yml down

Gives 0 of the 12 instructions most ship operate skills give in 524 tokens

Counted across 779 of the 1,178 authors here whose files we hold, read 2026-08-06

document a rollback plan before deploymentin 40 of 779, across 21 files
create an annotated git tagin 21 of 779, across 20 files
Run the test suitein 20 of 779
update the changelogin 20 of 779, across 18 files
verify deployment health after launchin 19 of 779, across 10 files
clean up feature flags after full rolloutin 18 of 779, across 10 files
verify the working tree is cleanin 18 of 779
test both feature flag statesin 17 of 779, across 9 files
Make database migrations backward-compatiblein 16 of 779, across 8 files
set up error monitoring before launchin 15 of 779, across 7 files
monitor metrics at each rollout stagein 14 of 779, across 5 files
create a github releasein 14 of 779

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.