devops-automation
CI/CD pipeline design with GitHub Actions, Docker, Kubernetes, Helm, and GitOps patterns
Profile →npx skills add rohitg00/awesome-claude-code-toolkit --skill devops-automation --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# DevOps Automation ## GitHub Actions Workflow Structure ```yaml name: CI/CD on: push: branches: [main] pull_request: branches: [main] concurrency: group: ${{ github.workflow }}-${{ github.ref }} cancel-in-progress: true jobs: lint: runs-on: ubuntu-latest steps: - uses: actions/checkout@v4 - uses: actions/setup-node@v4 with: node-version: 22 cache: 'npm' - run: npm ci - run: npm run lint test: runs-on: ubuntu-latest needs: lint strategy: matrix: node-version: [20, 22] steps: - uses: actions/checkout@v4 - uses: actions/setup-node@v4 with: node-version: ${{ matrix.node-version }} cache: 'npm' - run: npm ci - run: npm test -- --coverage - uses: actions/upload-artifact@v4 with: name: coverage-${{ matrix.node-version }} path: coverage/ deploy: runs-on: ubuntu-latest needs: test if: github.ref == 'refs/heads/main' environment: production steps: - uses: actions/checkout@v4 - run: ./deploy.sh ``` Key patterns: - Use `concurrency` to cancel outdated runs - Cache dependencies with setup action's `cache` option - Use `needs` for job dependencies - Gate deploys with `environment` protection rules - Use matrix for cross-version testing ## Docker Multi-Stage Builds ```dockerfile FROM node:22-alp
- GitHub Actions Workflow Structure
- Docker Multi-Stage Builds
- Kubernetes Deployment Manifest
- Helm Chart Structure
- ArgoCD GitOps Pattern
- Monitoring Stack
- Pipeline Best Practices
What does the devops-automation skill do?
CI/CD pipeline design with GitHub Actions, Docker, Kubernetes, Helm, and GitOps patterns
How do I install it?
Run `npx skills add rohitg00/awesome-claude-code-toolkit --skill devops-automation --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From rohitg00/awesome-claude-code-toolkit, a repository with 2,438 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.