Devops

Skill jjmendezrodriguez/jm-claude-plugin/skills/devops

DevOps and CI/CD best practices for TypeScript/Node projects using pnpm and GitHub Actions. Use this when setting up CI pipelines, configuring GitHub Actions, designing deploy workflows, caching dependencies, gating merges, or troubleshooting CI failures. Trigger on: "set up CI", "GitHub Actions", "why is CI failing", "add lint step", "deploy workflow", any new repo bootstrapping, or any pipeline change. Apply proactively — never merge red.From its SKILL.md

Install

npx -y skills add jjmendezrodriguez/jm-claude-plugin --skill devops

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

4.7 KB, as published. Nobody here has run it

DevOps & CI/CD — pnpm / GitHub Actions

Staff Engineer standard: CI is the contract with main — green is mandatory, automation enforces it.

1. Core Principles

✅ Every PR runs the full pipeline before merge
✅ Cache dependencies — slow CI loses signal
✅ Fail fast: lint → test → build → audit
✅ Pin action versions (e.g. @v4), avoid @latest
✅ Secrets in GitHub Secrets, never in workflow YAML
✅ Required status checks on protected branches
❌ Never merge red. Never disable failing checks to ship

2. CI Pipeline (Minimum Standard)

1. Lint      → Code style + ESLint rules
2. Typecheck → tsc --noEmit
3. Test      → Unit + integration (Vitest)
4. Build     → Verify compilation
5. Audit     → Security vulnerabilities (pnpm audit)

Order matters: cheap checks first, expensive last. Lint catches 80% of issues in seconds.

3. GitHub Actions — Reference Workflow

# .github/workflows/ci.yml
name: CI

on:
  push:
    branches: [main]
  pull_request:

jobs:
  ci:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4

      - uses: pnpm/action-setup@v4
        with:
          version: 9
          run_install: false

      - uses: actions/setup-node@v4
        with:
          node-version: 20
          cache: "pnpm"

      - run: pnpm install --frozen-lockfile
      - run: pnpm lint
      - run: pnpm typecheck
      - run: pnpm test
      - run: pnpm build
      - run: pnpm audit --audit-level=high

Rules:

--frozen-lockfile — fail if pnpm-lock.yaml drifts (CI must match lockfile exactly)
cache: "pnpm" — speeds up subsequent runs ~10x
Pin pnpm/action-setup@v4 and actions/setup-node@v4 to majors

4. Branch Naming (mirrors code-git skill)

feature/user-authentication    # New features
fix/api-timeout-error          # Bug fixes
hotfix/security-patch          # Critical production fixes
refactor/database-queries      # Internal cleanup
docs/update-readme             # Documentation only
chore/update-eslint            # Maintenance

Lowercase, hyphens, 3-5 words. Branch name should explain the change, not the ticket.

5. When CI Fails

NEVER:  Merge when CI is red
NEVER:  Disable a failing check to unblock yourself
NEVER:  Add `if: always()` to skip a step you don't understand
ALWAYS: Reproduce locally first — `pnpm <step>` with same Node version
ALWAYS: Push the fix, wait for green, then merge

Common failure patterns:

Symptom	Likely cause	Fix
`frozen-lockfile` error	Lockfile out of sync	Run `pnpm install` locally, commit `pnpm-lock.yaml`
Test passes local, fails CI	Timezone / locale / flaky timing	Pin `TZ=UTC` in workflow env, mock dates
Build OOM	Memory-heavy bundler step	Add `NODE_OPTIONS=--max-old-space-size=4096`
Audit fails on transitive dep	Upstream advisory	Override via `pnpm.overrides` in package.json

6. Secrets & Environment

# Reference, never inline
- run: pnpm deploy
  env:
    SUPABASE_SERVICE_ROLE_KEY: ${{ secrets.SUPABASE_SERVICE_ROLE_KEY }}