deployment

Skill — Deployment

This skill defines how to prepare, execute, and validate a deployment. An agent loaded with this skill knows what to check before deploying, how to do it, and how to confirm everything works.

---

When to invoke this skill

• Before each production release
• When setting up a CI/CD pipeline
• After a critical fix that needs to ship quickly
• To document the deployment procedure for a new project

---

Procedure

1. Pre-deployment — Checklist

Before any deployment, verify each point:

Code

• All tests pass (unit + E2E)
• The branch is up to date with the main branch
• No merge conflicts
• No forgotten TODO or temporary code
• No hardcoded secrets (API keys, passwords, tokens)

Dependencies

• Dependencies are locked (lock file up to date)
• No dependency added without justification in the issue
• Production versions are consistent with development

Configuration

• Production environment variables are set
• URLs, ports, and paths point to production (not dev)
• Database migrations are ready and reversible

Review

• The PR has been reviewed (code-review skill)
• The issue's done criteria are met
• The human has approved the deployment

2. Deployment — Execution

The deployment follows the pipeline defined by the project. Common formats:

Via CI/CD (recommended)

# Merging to the production branch triggers the pipeline
git checkout main
git merge --no-ff feat/ISS-XXXX-slug
git push origin main
# -> CI/CD takes over (build, test, deploy)

Via manual command

# 1. Build
npm run build          # or python -m build, cargo build --release, etc.

# 2. Production test
npm run test:prod      # tests on the production build

# 3. Deploy
npm run deploy         # or rsync, scp, docker push, kubectl apply, etc.

Rollback — always plan for it

Before deploying, make sure a rollback is possible:

# Identify the current version in production
git log --oneline -1 origin/production

# In case of a problem
git revert HEAD
git push origin main
# or: redeploy the previous tag