/deploy
Deploys with pre-flight checks and health verification. Triggers: deploy, deployment, ship, release, push to prod.
$ npx -y skills add softspark/ai-toolkit --skill deploy --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/deploy
Context preview
The summary Claude sees to decide when to auto-load this skill.
Deploys with pre-flight checks and health verification. Triggers: deploy, deployment, ship, release, push to prod.
SKILL.md
deploy.SKILL.mdname: deploy
description: "Deploys with pre-flight checks and health verification. Triggers: deploy, deployment, ship, release, push to prod."
effort: medium
disable-model-invocation: true
argument-hint: "[environment]"
allowed-tools: Bash, Read
hooks:
PostToolUse:
- matcher: "Bash"
hooks:
- type: command
command: "echo 'Reminder: verify health checks pass after deployment'"
scripts:
- scripts/pre_deploy_check.pyDeploy Application
$ARGUMENTS
Deploy application to target environment.
Project context
- Docker config: !`cat docker-compose.yml 2>/dev/null || cat Dockerfile 2>/dev/null || echo "no-docker"`
Usage
/deploy [environment]
What This Command Does
1. **Validates** deployment prerequisites 2. **Runs** pre-deployment checks 3. **Executes** deployment 4. **Verifies** deployment success
Environments
| Environment | Description | |-------------|-------------| | `dev` | Development environment | | `staging` | Staging/QA environment | | `prod` | Production environment |
Pre-Deployment Checklist
Run automated pre-deployment checks:
python3 ${CLAUDE_SKILL_DIR}/scripts/pre_deploy_check.py [environment]Returns JSON with pass/fail for each check:
- `git_clean` - no uncommitted changes
- `branch` - on main/master for production
- `docker` - services running (if applicable)
- `env_file` - .env or .env.$ENV exists
- `build_artifacts` - dist/build present
- `tests_ran` - test result artifacts found
Manual verification:
- [ ] Tests passing
- [ ] Build successful
- [ ] Environment variables set
- [ ] Secrets configured
- [ ] Database migrations ready
- [ ] Rollback plan documented
Deployment Strategies
| Strategy | Use Case | |----------|----------| | Rolling | Zero-downtime, gradual | | Blue-Green | Instant switch, easy rollback | | Canary | Risk mitigation, gradual traffic | | Recreate | Simple, allows downtime |
Output Format
## Deployment Report
### Status: Success / Failed
### Details
- **Environment**: [env]
- **Version**: [version]
- **Started**: [timestamp]
- **Completed**: [timestamp]
### Steps
1. [Step 1] - Done
2. [Step 2] - Done
3. [Step 3] - Failed (if failed)
### Health Check
- [endpoint]: [status]
### Rollback
If needed: `[rollback command]`
PRODUCTION SAFETY
- Always deploy to staging first
- Verify health checks pass
- Have rollback plan ready
- Monitor after deployment
MANDATORY: Documentation Update
After deployment, update documentation:
Required Updates
| Change Type | Update | |-------------|--------| | New release | CHANGELOG, release notes | | Config changes | Deployment docs, procedures | | New features | User documentation | | Infrastructure | `kb/procedures/deployment-*.md` |
Post-Deployment Checklist
- [ ] Deployment successful
- [ ] Health checks passing
- [ ] **CHANGELOG updated**
- [ ] **Deployment docs updated**
- [ ] Release notes created (if applicable)
Read more
name: deploy
description: "Deploys with pre-flight checks and health verification. Triggers: deploy, deployment, ship, release, push to prod."
effort: medium
disable-model-invocation: true
argument-hint: "[environment]"
allowed-tools: Bash, Read
hooks:
PostToolUse:
- matcher: "Bash"
hooks:
- type: command
command: "echo 'Reminder: verify health checks pass after deployment'"
scripts:
- scripts/pre_deploy_check.pyDeploy Application
$ARGUMENTS
Deploy application to target environment.
Project context
- Docker config: !`cat docker-compose.yml 2>/dev/null || cat Dockerfile 2>/dev/null || echo "no-docker"`
Usage
/deploy [environment]
What This Command Does
1. **Validates** deployment prerequisites 2. **Runs** pre-deployment checks 3. **Executes** deployment 4. **Verifies** deployment success
Environments
| Environment | Description | |-------------|-------------| | `dev` | Development environment | | `staging` | Staging/QA environment | | `prod` | Production environment |
Pre-Deployment Checklist
Run automated pre-deployment checks:
python3 ${CLAUDE_SKILL_DIR}/scripts/pre_deploy_check.py [environment]Returns JSON with pass/fail for each check:
- `git_clean` - no uncommitted changes
- `branch` - on main/master for production
- `docker` - services running (if applicable)
- `env_file` - .env or .env.$ENV exists
- `build_artifacts` - dist/build present
- `tests_ran` - test result artifacts found
Manual verification:
- [ ] Tests passing
- [ ] Build successful
- [ ] Environment variables set
- [ ] Secrets configured
- [ ] Database migrations ready
- [ ] Rollback plan documented
Deployment Strategies
| Strategy | Use Case | |----------|----------| | Rolling | Zero-downtime, gradual | | Blue-Green | Instant switch, easy rollback | | Canary | Risk mitigation, gradual traffic | | Recreate | Simple, allows downtime |
Output Format
## Deployment Report ### Status: Success / Failed ### Details - **Environment**: [env] - **Version**: [version] - **Started**: [timestamp] - **Completed**: [timestamp] ### Steps 1. [Step 1] - Done 2. [Step 2] - Done 3. [Step 3] - Failed (if failed) ### Health Check - [endpoint]: [status] ### Rollback If needed: `[rollback command]`
PRODUCTION SAFETY
- Always deploy to staging first
- Verify health checks pass
- Have rollback plan ready
- Monitor after deployment
MANDATORY: Documentation Update
After deployment, update documentation:
Required Updates
| Change Type | Update | |-------------|--------| | New release | CHANGELOG, release notes | | Config changes | Deployment docs, procedures | | New features | User documentation | | Infrastructure | `kb/procedures/deployment-*.md` |
Post-Deployment Checklist
- [ ] Deployment successful
- [ ] Health checks passing
- [ ] **CHANGELOG updated**
- [ ] **Deployment docs updated**
- [ ] Release notes created (if applicable)
Professional-grade AI coding toolkit with multi-platform support. Machine-enforced safety, 109 skills, 44 agents, expanded lifecycle hooks, persona presets, experimental opt-in plugin packs, and benchmark tooling — works with Claude Code, Claude Chat/Cowork,
Repo: softspark/ai-toolkit
Other skills on ai-toolkit.
- /ai-toolkit-rules
Mandatory engineering, security, testing, git, performance, quality, and response rules. Claude MUST load this skill for every technical, coding, debugging, review, architecture, DevOps, data, or file-editing task in Chat or Cowork.
Open skill - /mem-search
Search past coding sessions using natural language. Finds relevant observations, decisions, and context from previous work.
Open skill - /a11y-validate
Accessibility validator: WCAG 2.1 AA, EN 301 549, EAA. Triggers: a11y, accessibility, WCAG, EAA, ARIA, contrast, keyboard, screen reader.
Open skill - /agent-creator
Creates new specialized agents with frontmatter, tools, delegation. Triggers: new agent, create agent, agent scaffold, specialized agent.
Open skill - /analyze
Analyzes code quality, complexity, patterns across codebase. Triggers: quality report, hotspot scan, code analysis, architecture signal.
Open skill - /api-patterns
REST/GraphQL API design: naming, versioning, pagination, idempotency, OpenAPI. Triggers: API design, REST, GraphQL, OpenAPI, Swagger, idempotency, rate limit.
Open skill

