From framework-dev
Use when designing CI/CD pipelines or creating GitHub Actions / GitLab CI configuration.
How this skill is triggered — by the user, by Claude, or both
Slash command
/framework-dev:deployment-pipeline-designThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
This skill guides CI/CD pipeline design during framework planning, providing templates and best practices for automated build, test, and deployment workflows.
This skill guides CI/CD pipeline design during framework planning, providing templates and best practices for automated build, test, and deployment workflows.
┌─────────┐ ┌─────────┐ ┌─────────┐ ┌─────────┐ ┌─────────┐
│ Build │──▶│ Test │──▶│ Scan │──▶│ Stage │──▶│ Prod │
└─────────┘ └─────────┘ └─────────┘ └─────────┘ └─────────┘
│ │ │ │ │
▼ ▼ ▼ ▼ ▼
Compile Unit Tests Security Deploy to Deploy to
Lint Integration SAST/DAST Staging Production
Type Check E2E Tests Deps Audit Smoke Test Health Check
See references/github-actions-template.yml for the complete pipeline configuration. The template includes jobs for build (lint, type-check, compile), test (unit + integration with coverage), security (audit + SAST), and deployments to staging/production with artifact management and environment-specific smoke tests.
See references/gitlab-ci-template.yml for the complete pipeline configuration. The template includes 5 stages (build, test, security, staging, production) with service containers for integration tests (postgres, redis), coverage reporting, and branch-based deployment rules with manual approval for production.
Feature Branch → develop → staging → main → production
│ │ │ │ │
▼ ▼ ▼ ▼ ▼
PR Tests Integration QA Test Final Live
Tests Manual Review
| Environment | Purpose | Data | Access |
|---|---|---|---|
| Development | Local dev | Fake/seed | Developer |
| CI | Automated tests | Test fixtures | CI only |
| Staging | Pre-production | Anonymized prod | Team |
| Production | Live | Real | Restricted |
┌─────────────┐
│ Load │
│ Balancer │
└──────┬──────┘
│
┌───────┴───────┐
│ │
┌──────▼──────┐ ┌──────▼──────┐
│ Blue │ │ Green │
│ (v1.0) │ │ (v1.1) │
│ [ACTIVE] │ │ [STANDBY] │
└─────────────┘ └─────────────┘
1. Deploy to Green (standby)
2. Test Green
3. Switch traffic to Green
4. Blue becomes standby
┌─────────────┐
│ Load │
│ Balancer │
└──────┬──────┘
│
┌──────────┼──────────┐
│ │ │
▼ (90%) ▼ (10%) │
┌───────────┐ ┌───────────┐
│ Stable │ │ Canary │
│ (v1.0) │ │ (v1.1) │
└───────────┘ └───────────┘
1. Deploy canary with 10% traffic
2. Monitor metrics
3. Gradually increase to 100%
4. Rollback if issues
Time 0: [v1] [v1] [v1] [v1]
Time 1: [v2] [v1] [v1] [v1]
Time 2: [v2] [v2] [v1] [v1]
Time 3: [v2] [v2] [v2] [v1]
Time 4: [v2] [v2] [v2] [v2]
# Use in workflow
env:
DATABASE_URL: ${{ secrets.DATABASE_URL }}
API_KEY: ${{ secrets.API_KEY }}
# Or per-step
- name: Deploy
env:
TOKEN: ${{ secrets.DEPLOY_TOKEN }}
run: deploy.sh
| Secret | Environment | Purpose |
|---|---|---|
DATABASE_URL | staging, production | Database connection |
JWT_SECRET | staging, production | Token signing |
DEPLOY_TOKEN | CI | Deployment auth |
CODECOV_TOKEN | CI | Coverage reporting |
Before deploying:
During Phase 3 (Planning) or Phase 6 (Integration):
npx claudepluginhub ankurjain1121/dev-workflow-skills --plugin framework-devDesigns CI/CD pipelines with build/test/deploy stages, blue-green/canary/rolling deployments, feature flags, artifact management, and environment promotion strategies. Use for setting up or improving pipelines and workflows.
Designs multi-stage CI/CD pipelines with approval gates and deployment strategies including rolling, canary, and blue-green.
GitHub Actions, GitLab CI, Jenkins; stages, artifacts, caching, and deployment automation.