Section 01: DevOps & CI/CD Integration

GitHub Actions Integration

Automated PR Review & Release

name: Claude Code Review
on:
  pull_request:
    types: [opened, synchronize]

jobs:
  review:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v3
        with:
          fetch-depth: 0
      
      - name: Install Claude CLI
        run: curl -fsSL https://claude.ai/install.sh | sh
      
      - name: Review PR
        env:
          ANTHROPIC_API_KEY: $
        run: |
          git diff origin/$... | \
          claude "Review for:
          - Security vulnerabilities
          - Performance issues
          - Code quality concerns
          - Breaking changes
          Provide specific file:line references" > review.md
      
      - name: Comment on PR
        uses: actions/github-script@v6
        with:
          script: |
            const fs = require('fs');
            const review = fs.readFileSync('review.md', 'utf8');
            github.rest.issues.createComment({
              issue_number: context.issue.number,
              owner: context.repo.owner,
              repo: context.repo.repo,
              body: review
            });

Review criteria for AI-generated code: PR Review Guide.

Release Notes Generation

# Generate release notes from commits
git log $(git describe --tags --abbrev=0 HEAD^)..HEAD --oneline | \
claude "Generate release notes:
## New Features
## Bug Fixes
## Breaking Changes
## Improvements
Use conventional commit format"

Infrastructure as Code

Terraform Generation

# Generate Terraform for AWS ECS
claude "Generate Terraform for:
- ECS Fargate cluster
- Load balancer (ALB)
- Auto-scaling (2-10 tasks)
- CloudWatch logging
- IAM roles with least privilege
Output: main.tf, variables.tf, outputs.tf"

Kubernetes Manifests

# Generate K8s deployment
claude "Generate Kubernetes manifests for Node.js API:
- Deployment (3 replicas)
- Service (ClusterIP)
- HorizontalPodAutoscaler
- ConfigMap for env vars
- Secret for API keys
- Ingress with TLS
Follow best practices for: security, resources, probes"

Docker Optimization

# Optimize Dockerfile with multi-stage builds
claude "@Dockerfile Optimize for:
- Smaller image size (use multi-stage)
- Faster builds (layer caching)
- Security (non-root user, minimal base)
- Best practices (COPY vs ADD, etc.)"

← Back to Part 4 Index

Next: Architecture Design →