agentleFS
Sign inStart free
salmandevsalmandev/everything-gemini/skills/devops-pipeline/SKILL.md

devops-pipeline

Skill2 starsChanged 28 days agoApache-2.0View on GitHub

Architects and configures Docker containers, multi-stage Dockerfiles, GitHub Actions CI/CD workflows, and infrastructure automation. Use when building or tuning deployment pipelines.

3 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 3 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

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

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

    Use multi-stage builds (AS builder and AS runner) to keep final image sizes minimal (< 100MB).

    line 14
  2. Very specific:

    Run applications as a non-root user (USER node or USER appuser) for defense-in-depth.

    line 15
  3. Distinctive:

    Run linting, typechecking, and unit tests concurrently using GitHub Actions job matrix.

    line 20

“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

DevOps Pipeline Engineering

This skill structures Docker containerization, caching, security scanning, and CI/CD automation.

Core Directives

1. Minimal Multi-Stage Dockerfiles

  • Use multi-stage builds (AS builder and AS runner) to keep final image sizes minimal (< 100MB).
  • Run applications as a non-root user (USER node or USER appuser) for defense-in-depth.
  • Order commands to maximize Docker layer cache hits (copy package.json / requirements.txt before copying source code).

2. GitHub Actions CI/CD Best Practices

  • Cache dependencies (actions/cache or actions/setup-node with cache: 'npm').
  • Run linting, typechecking, and unit tests concurrently using GitHub Actions job matrix.
  • Enforce status checks before permitting branch merges into main.

For complete production CI/CD workflow templates, see templates/github-ci.yml.

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