artubss/SKILLS-CLAUDE-CODE / favorites/tpl-devops-github-actions-cicd
tpl-devops-github-actions-cicd
UnverifiedTemplate do pack (devops/01-github-actions-cicd.md). Orienta o agente em infra, deploy, CI/CD e operacao alinhado a esse contexto.
PROJECT: GitHub Actions CI/CD Pipeline (Docker + ECR/DockerHub + Node.js/Python)
Skill gerado a partir do pack templates-claude-code. Arquivo de origem: devops/01-github-actions-cicd.md. Use como baseline e adapte ao projeto antes de mudancas grandes.
Conteudo do template
STACK
- CI/CD: GitHub Actions
- Containerization: Docker + multi-stage builds
- Registry: AWS ECR (or DockerHub fallback)
- Language: Node.js 20 / Python 3.12
- Testing: Jest / Pytest
- Linting: ESLint + Prettier / Ruff + mypy
- Deployment target: ECS Fargate / EC2 / Lambda
WORKFLOW STRUCTURE
.github/
└── workflows/
├── ci.yml # Lint + test on every PR
├── build.yml # Docker build + push on merge to main
├── deploy-staging.yml
└── deploy-prod.yml # Manual approval gate
ARCHITECTURE RULES
- CI runs on every PR — never merge code that hasn't passed lint + test.
- Build only on merge to main — do not push images from feature branches.
- One image, multiple tags — tag with
git sha+latest+ semver if tagged release. - Secrets via GitHub Secrets only — never hardcode credentials; use
${{ secrets.KEY }}. - Cache aggressively — npm/pip dependencies and Docker layer cache cut 60–80% of runtime.
- Environment protection rules —
productionenvironment requires 1 reviewer approval. - Reusable workflows — extract
build-and-pushinto a callable workflow; call from deploy workflows. - Fail fast, explicit — use
fail-fast: truein matrix, settimeout-minuteson every job.
CI WORKFLOW — LINT + TEST
# .github/workflows/ci.yml
name: CI
on:
pull_request:
branches: [main, develop]
push:
branches: [main]
permissions:
contents: read
pull-requests: write
jobs:
lint:
name: Lint
runs-on: ubuntu-24.04
steps:
- uses: actions/checkout@v4
- name: Setup Node.js
uses: actions/setup-node@v4
with:
node-version: '20'
cache: 'npm'
- name: Install dependencies
run: npm ci --prefer-offline
- name: Run ESLint
run: npm run lint
- name: Run Prettier check
run: npm run format:check
test:
name: Test
runs-on: ubuntu-24.04
needs: lint
services:
postgres:
image: postgres:16-alpine
env:
POSTGRES_PASSWORD: testpass
POSTGRES_DB: testdb
options: >-
--health-cmd pg_isready
--health-interval 10s
--health-timeout 5s
--health-retries 5
ports: ['5432:5432']
redis:
image: redis:7-alpine
options: >-
--health-cmd "redis-cli ping"
--health-interval 10s
ports: ['6379:6379']
steps:
- uses: actions/checkout@v4
- name: Setup Node.js
uses: actions/setup-node@v4
with:
node-version: '20'
cache: 'npm'
- name: Install dependencies
run: npm ci --prefer-offline
- name: Run migrations
run: npm run db:migrate
env:
DATABASE_URL: postgresql://postgres:testpass@localhost:5432/testdb
- name: Run tests
run: npm test -- --coverage --ci
env:
NODE_ENV: test
DATABASE_URL: postgresql://postgres:testpass@localhost:5432/testdb
REDIS_URL: redis://localhost:6379
- name: Upload coverage
uses: codecov/codecov-action@v4
with:
token: ${{ secrets.CODECOV_TOKEN }}
BUILD + PUSH WORKFLOW
# .github/workflows/build.yml
name: Build & Push
on:
push:
branches: [main]
workflow_call:
outputs:
image-tag:
description: "Full image URI with tag"
value: ${{ jobs.build.outputs.image-tag }}
permissions:
id-token: write # OIDC for AWS auth (no long-lived keys)
contents: read
jobs:
build:
name: Build & Push to ECR
runs-on: ubuntu-24.04
outputs:
image-tag: ${{ steps.meta.outputs.tags }}
steps:
- uses: actions/checkout@v4
- name: Configure AWS credentials (OIDC)
uses: aws-actions/configure-aws-credentials@v4
with:
role-to-assume: ${{ secrets.AWS_ROLE_ARN }}
aws-region: us-east-1
- name: Login to Amazon ECR
id: ecr-login
uses: aws-actions/amazon-ecr-login@v2
- name: Set up Docker Buildx
uses: docker/setup-buildx-action@v3
- name: Docker metadata
id: meta
uses: docker/metadata-action@v5
with:
images: ${{ steps.ecr-login.outputs.registry }}/my-app
tags: |
type=sha,prefix=,format=short
type=raw,value=latest,enable={{is_default_branch}}
type=semver,pattern={{version}}
- name: Build and push
uses: docker/build-push-action@v5
with:
context: .
push: true
tags: ${{ steps.meta.outputs.tags }}
cache-from: type=gha
cache-to: type=gha,mode=max
build-args: |
NODE_ENV=production
BUILD_DATE=${{ github.event.head_commit.timestamp }}
GIT_SHA=${{ github.sha }}
DEPLOY WORKFLOW (WITH ENVIRONMENT PROTECTION)
# .github/workflows/deploy-prod.yml
name: Deploy Production
on:
workflow_dispatch:
inputs:
image-tag:
description: 'Image SHA tag to deploy'
required: true
jobs:
deploy:
name: Deploy to Production ECS
runs-on: ubuntu-24.04
environment:
name: production # Requires reviewer approval in GitHub settings
url: https://myapp.com
steps:
- name: Configure AWS credentials
uses: aws-actions/configure-aws-credentials@v4
with:
role-to-assume: ${{ secrets.AWS_PROD_ROLE_ARN }}
aws-region: us-east-1
- name: Download task definition
run: |
aws ecs describe-task-definition \
--task-definition my-app-prod \
--query taskDefinition > task-def.json
- name: Update image in task definition
id: task-def
uses: aws-actions/amazon-ecs-render-task-definition@v1
with:
task-definition: task-def.json
container-name: app
image: ${{ secrets.ECR_REGISTRY }}/my-app:${{ github.event.inputs.image-tag }}
- name: Deploy ECS service
uses: aws-actions/amazon-ecs-deploy-task-definition@v1
with:
task-definition: ${{ steps.task-def.outputs.task-definition }}
service: my-app-prod
cluster: production
wait-for-service-stability: true
CACHING STRATEGIES
# npm cache (set in setup-node above via cache: 'npm')
# Manual cache for pip:
- name: Cache pip
uses: actions/cache@v4
with:
path: ~/.cache/pip
key: pip-${{ hashFiles('**/requirements*.txt') }}
restore-keys: pip-
# Docker layer cache uses type=gha (GitHub Actions cache) in build-push-action
# This is the most effective: saves 2-4 min on typical Node builds.
SECRETS MANAGEMENT RULES
- AWS auth: Use OIDC (aws-actions/configure-aws-credentials) — NEVER store ACCESS_KEY_ID
- DB passwords: GitHub Secrets only, never in workflow YAML values
- NPM_TOKEN: Set in org-level secrets, not repo-level, to share across repos
- Rotation: Rotate secrets every 90 days; use AWS Secrets Manager for app runtime secrets
BRANCH PROTECTION (Settings → Branches → main)
✅ Require PR before merging
✅ Require 1 approving review
✅ Dismiss stale reviews on new commits
✅ Require status checks: lint, test
✅ Require branches to be up to date
✅ Restrict pushes to main (no direct push)
✅ Include administrators
PYTHON VARIANT (pip + pytest)
test-python:
runs-on: ubuntu-24.04
strategy:
matrix:
python-version: ['3.11', '3.12']
steps:
- uses: actions/checkout@v4
- uses: actions/setup-python@v5
with:
python-version: ${{ matrix.python-version }}
cache: 'pip'
- run: pip install -r requirements-dev.txt
- name: Lint with Ruff
run: ruff check .
- name: Type check
run: mypy app/ --ignore-missing-imports
- name: Run tests
run: pytest -v --cov=app --cov-report=xml
env:
ENVIRONMENT: test
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deployment | Stars: 318k | Updated | Claude CodeCodex | Unverified | Install |
| xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |
| shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |
| childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release. | Stars: 117k | Updated | Claude CodeCodex | Unverified | Install |