Skip to content
Back to skills

Ci Cd Pipeline

ASecurity

Automated CI/CD pipeline setup with GitHub Actions, deployment strategies, and automation workflows. Use for build automation, testing, and deployment.

  • 33 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added February 10, 2026
devopsnodedockertestinggitapidatabaseci/cdsecurity

Works with

  • api

Security analysis

A100/100

Scanned February 12, 2026

npx -y skills add lovedragonball/power-ranger-toolkit --skill ci-cd-pipeline --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Ci Cd Pipeline?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Ci Cd Pipeline
[![Security: A β€” Skills Directory](https://www.skillsdirectory.com/api/skills/lovedragonball-ci-cd-pipeline/badge)](https://www.skillsdirectory.com/skills/lovedragonball-ci-cd-pipeline)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: ci-cd-pipeline
description: Automated CI/CD pipeline setup with GitHub Actions, deployment strategies, and automation workflows. Use for build automation, testing, and deployment.
---

# πŸš€ CI/CD Pipeline Skill

## GitHub Actions Workflows

### Basic CI Workflow
```yaml
# .github/workflows/ci.yml
name: CI
on:
  push:
    branches: [main, develop]
  pull_request:
    branches: [main]

jobs:
  build:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - uses: actions/setup-node@v4
        with:
          node-version: '20'
          cache: 'npm'
      - run: npm ci
      - run: npm run lint
      - run: npm test
      - run: npm run build
```

### Deploy to Vercel
```yaml
# .github/workflows/deploy.yml
name: Deploy
on:
  push:
    branches: [main]

jobs:
  deploy:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - uses: amondnet/vercel-action@v25
        with:
          vercel-token: ${{ secrets.VERCEL_TOKEN }}
          vercel-org-id: ${{ secrets.VERCEL_ORG_ID }}
          vercel-project-id: ${{ secrets.VERCEL_PROJECT_ID }}
          vercel-args: '--prod'
```

---

## Deployment Strategies

| Strategy | Description | Risk | Rollback |
|----------|-------------|------|----------|
| Rolling | Replace instances gradually | Low | Slow |
| Blue-Green | Switch between environments | Low | Fast |
| Canary | Route % traffic to new version | Medium | Fast |
| Recreate | Stop old, start new | High | Slow |

---

## Environment Management

### Secrets Setup
```yaml
env:
  DATABASE_URL: ${{ secrets.DATABASE_URL }}
  API_KEY: ${{ secrets.API_KEY }}

# Environment-specific
jobs:
  deploy-staging:
    environment: staging
  deploy-production:
    environment: production
    needs: deploy-staging
```

### Branch Protection
```yaml
on:
  push:
    branches:
      - main      # Production
      - develop   # Staging
      - 'feature/*'  # Feature branches
```

---

## Docker Build Pipeline

```yaml
jobs:
  docker:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      
      - name: Login to Docker Hub
        uses: docker/login-action@v3
        with:
          username: ${{ secrets.DOCKER_USERNAME }}
          password: ${{ secrets.DOCKER_PASSWORD }}
      
      - name: Build and push
        uses: docker/build-push-action@v5
        with:
          push: true
          tags: user/app:latest
```

---

## Pipeline Checklist

- [ ] Lint code
- [ ] Run unit tests
- [ ] Run integration tests
- [ ] Build application
- [ ] Security scan (SAST)
- [ ] Deploy to staging
- [ ] Run E2E tests
- [ ] Deploy to production
- [ ] Health check
- [ ] Notify team

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…