deployment-sop
/deployment-sop
Deployment workflows, pre-deploy validation, and smoke testing patterns. Use when deploying to staging or production, running smoke tests, or validating deployments.
- Author
- bybren-llc ↗
- Repository
- safe-agentic-workflow ↗
- Licence
- MIT
- Last repository change
- 20.07.2026
Assessment and security
- Files in this package
- 2
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 3
No signals detected. Repository changed on 20.07.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Deployment workflows, pre-deploy validation, and smoke testing patterns. Use when deploying to staging or production, running smoke tests, or validating deployments.
Original author description
Deployment workflows, pre-deploy validation, and smoke testing patterns. Use when deploying to staging or production, running smoke tests, or validating deployments.
How it works
- Purpose
- When This Skill Applies
- Authoritative References (MUST READ)
- Pre-Deployment Checklist
- Post-Deployment Smoke Test
- Deployment Evidence Template
- Rollback Procedure
- Stop-the-Line Conditions
- Branch → Environment Mapping
SKILL.md preview
---
name: deployment-sop
description: Deployment workflows, pre-deploy validation, and smoke testing patterns. Use when deploying to staging or production, running smoke tests, or validating deployments.
---
# Deployment SOP Skill
## Purpose
Route to existing deployment SOPs and provide checklists for safe, validated deployments. This skill does NOT duplicate SOP content—it links to authoritative sources.
## When This Skill Applies
- Deploying to staging or production
- Running pre-deploy validation
- Executing post-deploy smoke tests
- Accessing development machines for deployment
- Coordinating release activities
## Authoritative References (MUST READ)
| Document | Location | Purpose |
| ------------------------ | ------------------------------------------------- | --------------------------- |
| Semantic Release SOP | `docs/ci-cd/Semantic-Release-Deployment-SOP.md` | Release automation workflow |
| Staging/UAT Release SOP | `docs/sop/STAGING-UAT-RELEASE-SOP.md` | UAT validation process |
| Linux Dev Machine Access | `docs/deployment/LINUX-DEV-MACHINE-ACCESS-SOP.md` | Dev server access |
| Production Server Access | `docs/deployment/PRODUCTION-SERVER-ACCESS-SOP.md` | Production deployment |
## Pre-Deployment Checklist
Before ANY deployment:
- [ ] All CI checks pass (GitHub Actions green)
- [ ] PR merged to target branch
- [ ] No unresolved blockers in Linear
- [ ] Database migrations tested locally
- [ ] Environment variables verified
```bash
# Validate before deploy
yarn ci:validate
yarn build
```
## Post-Deployment Smoke Test
After deployment completes:
- [ ] Health endpoint responds: `curl https://{domain}/api/health`
- [ ] Database connection verified (check health response)
- [ ] Authentication flow works (sign-in/sign-up)
- [ ] Critical user flows functional
- [ ] No new errors in logs
```bash
# Smoke test commands
curl -s https://{domain}/api/health | jq .
# Expected: {"status":"healthy","timestamp":"..."}
```
## Deployment Evidence Template
For Linear ticket attachment:
```markdown
## Deployment Evidence - {{TICKET_PREFIX}}-XXX
### Environment
- **Target**: Staging / Production
- **Branch**: `{branch_name}`
- **Commit**: `{commit_sha}`
### Pre-Deployment
- [x] CI checks passed
- [x] PR merged
- [x] Migrations verified
### Post-Deployment
- [x] Health check: PASSED
- [x] Auth flow: PASSED
- [x] Smoke tests: PASSED
### Verification
curl -s https://{domain}/api/health
{"status":"healthy","timestamp":"2025-XX-XXTXX:XX:XX.XXXZ"}
```
## Rollback Procedure
If deployment fails:
1. **Identify failure** - Check logs, monitoring dashboards
2. **Revert commit** - `git revert {commit_sha}`
3. **Push revert** - Triggers automatic rollback deployment
4. **Verify rollback** - Run smoke tests again
5. **Document incident** - Update Linear ticket with evidence
## Stop-the-Line Conditions
### FORBIDDEN
- Deploying with failing CI checks
- Skipping smoke tests on production
- Deploying database migrations without local testing
- Force-deploying over active incidents
### REQUIRED
- Health check MUST pass within 5 minutes
- Production deployments MUST have staging validation first
- Rollback plan MUST be documented before production deploy
## Branch → Environment Mapping
| Branch | Environment | Auto-Deploy |
| -------- | ----------- | ----------- |
| `dev` | Staging | Manual pull |
| `main` | Production | Automatic |
**Note**: Merging to `dev` builds Docker image but requires manual pull on staging server.
Files in this package (2)
- README.md 2 KB
- SKILL.md 4 KB
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · bybren-llc/safe-agentic-workflow | 100 | MIT |
| bybren-llc/safe-agentic-workflow | 100 | MIT |
Database snapshot: 13.11.2026 · package version e1281feac162 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 95staging-validation-phase
Guides manual staging validation before production deployment through smoke tests, critical user flow testing, data migration verification, and rollback capability checks. Use when validating staging deployments, running pre-production tests, or preparing for production… - 100running-smoke-tests
Execute fast smoke tests validating critical functionality after deployment. Use when performing specialized testing. Trigger with phrases like "run smoke tests", "quick validation", or "test critical paths". - 100running-smoke-tests
Execute fast smoke tests validating critical functionality after deployment. Use when performing specialized testing. Trigger with phrases like "run smoke tests", "quick validation", or "test critical paths". - 100deployment-checklist
Run pre-deployment verification before pushing to staging or production — build, tests, env config, security, DB, infra, integration — and return a READY / NOT READY verdict. Trigger on: "pre-deploy check", "deployment checklist", "ready to ship", "is this ready for prod",… - 100nacl-tl-deploy
Monitor CI/CD deployment results, run health checks, and report deployment evidence for NaCl TL tasks. Use when checking deploy status, verifying a staging or production deployment, or when the user says `/nacl-tl-deploy`. - 84orchestrate-deployment
Orchestrate deployment pipelines and infrastructure. Use when user says "deploy to staging", "set up CI/CD for this project", "configure deployment pipeline", "deploy to production with canary", or "rollback the last deployment".