agentleFS
Sign inStart free
harrissohail6harrissohail6/claude-code-config/skills/ci-cd-pipelines/SKILL.md

ci-cd-pipelines

Skill1 starsChanged 11 months agoMITView on GitHub

CI/CD pipeline design and implementation. Auto-activates when discussing deployment, automation, or pipelines.

We split this skill into the rules it gives an agent

3 rules. 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 3 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Run linting first (fastest)

    line 73
  2. Distinctive:

    Run unit tests before integration

    line 74
  3. Distinctive:

    Use secrets for credentials

    line 78

“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

CI/CD Pipelines

GitHub Actions

Basic CI Pipeline

name: CI

on:
  push:
    branches: [main]
  pull_request:
    branches: [main]

jobs:
  test:
    runs-on: ubuntu-latest
    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

      - name: Run linter
        run: npm run lint

      - name: Run tests
        run: npm test

      - name: Build
        run: npm run build

CD Pipeline

  deploy:
    needs: test
    runs-on: ubuntu-latest
    if: github.ref == 'refs/heads/main'

    steps:
      - uses: actions/checkout@v4

      - name: Deploy to production
        env:
          DEPLOY_TOKEN: ${{ secrets.DEPLOY_TOKEN }}
        run: |
          ./deploy.sh

Pipeline Stages

┌──────┐   ┌──────┐   ┌───────┐   ┌────────┐   ┌────────┐
│ Lint │ → │ Test │ → │ Build │ → │ Deploy │ → │ Verify │
└──────┘   └──────┘   └───────┘   └────────┘   └────────┘

Best Practices

Fail Fast

  • Run linting first (fastest)
  • Run unit tests before integration
  • Cache dependencies

Security

  • Use secrets for credentials
  • Scan for vulnerabilities
  • Sign artifacts

Environments

develop → staging → production

Rollback Strategy

  • Keep previous deployments
  • Blue-green deployment
  • Feature flags for gradual rollout

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free