agentleFS
Sign inStart free
NikoxkxNikoxkx/Agent-Skills/skills/devops/github-actions-pipeline/SKILL.md

github-actions-pipeline

Skill1 starsChanged 5 months agoApache-2.0View on GitHub

Creates GitHub Actions CI/CD pipelines with build, test, lint, and deploy stages. Use when setting up or improving automated workflows in GitHub.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use actions/cache or actions/setup-node with cache for node_modules / pnpm store.

    line 40
  2. Distinctive:

    Flaky tests: Add retry logic or quarantine jobs.

    line 67
  3. Very specific:

    Long builds: Use actions/cache aggressively and consider self-hosted runners for very large repos.

    line 68
  4. Very specific:

    Secret leaks: Never echo secrets; use ::add-mask::.

    line 69
  5. Distinctive:

    Check Actions tab for clean logs and artifacts.

    line 75

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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

Overview

Designs complete, efficient GitHub Actions workflows for CI and CD. Includes triggers, job matrices, intelligent caching (npm/pip/pnpm/yarn), secret management, conditional execution, artifact handling, and deployment patterns to common platforms (Vercel, AWS, GCP, Fly.io, self-hosted).

When to Use This Skill

  • Setting up CI for a new repository.
  • Improving slow, flaky, or expensive existing pipelines.
  • Adding deployment automation.

Prerequisites

  • GitHub repository with Actions enabled.
  • Tests, linters, and build commands already defined in package.json / Makefile / etc.
  • Secrets configured in GitHub repo settings (or org level).

Steps

  1. Define triggers (on push to main, PRs, manual, schedule for nightly).
  2. Create jobs:
    • lint
    • test (with matrix for node versions or browsers if needed)
    • build
    • deploy (only on main, after tests pass)
  3. Caching:
    • Use actions/cache or actions/setup-node with cache for node_modules / pnpm store.
    • Cache Docker layers when building images.
  4. Secrets & environments:
    • Use ${{ secrets.VAR }}.
    • Protect production deploys with Environments + required reviewers.
  5. Conditional steps and needs: for dependency.
  6. Reusable workflows for common patterns across repos.
  7. Deployment examples:
    • Vercel (using vercel action or CLI).
    • AWS (ECS, Lambda, S3 + CloudFront).
    • Fly.io, Railway, Render, etc.
  8. Output:
    • Full .github/workflows/ci.yml and cd.yml (or combined).
    • Required secrets list.
    • How to add environments.

Examples

A production-grade CI workflow with pnpm caching, parallel jobs, and a CD workflow that deploys to Vercel on main (with preview deploys on PRs) is included, plus patterns for AWS and Docker-based deploys.

Edge Cases & Error Handling

  • Flaky tests: Add retry logic or quarantine jobs.
  • Long builds: Use actions/cache aggressively and consider self-hosted runners for very large repos.
  • Secret leaks: Never echo secrets; use ::add-mask::.

Verification

  1. Push a PR — CI runs and reports status.
  2. Merge to main — CD triggers and deploys successfully.
  3. Check Actions tab for clean logs and artifacts.
  4. Success: Every PR is validated, main is always deployable, deploys are automatic and safe.

References

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.

Reviews can't be read right now.

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