agentleFS
Sign inStart free
MRCalderon3DMRCalderon3D/everything-game-dev-code/skills/engineering-common/build-pipeline-patterns/SKILL.md

build-pipeline-patterns

Skill105 starsChanged 8 months agoMITView on GitHub

Structure build and CI pipelines so builds are reproducible, diagnosable, and release-friendly.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    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:

    test and artifact requirements

    line 22
  2. Distinctive:

    Keep this skill aligned with the relevant rules layer and current project documentation.

    line 58
  3. Distinctive:

    If engine-specific constraints materially change the workflow, hand off to the matching engine skill or engine-specific reviewer.

    line 59

≈ “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

Build Pipeline Patterns

Purpose

Structure build and CI pipelines so builds are reproducible, diagnosable, and release-friendly.

Use When

  • builds are fragile or manual
  • multiple platforms or configurations exist
  • release confidence depends on automation

Inputs

  • target platforms
  • environment setup
  • release process
  • test and artifact requirements

Process

  1. define build entry points and environment assumptions
  2. separate fast validation from full packaging
  3. attach logs, metadata, and artifacts consistently
  4. make versioning and configuration drift visible
  5. link builds to QA and release gates

Outputs

  • build pipeline model
  • artifact policy
  • CI stage map
  • release integration notes

Quality Bar

  • makes ownership, state flow, and failure behavior explicit
  • improves maintainability without over-abstracting
  • supports testing, debugging, and safe iteration

Common Failure Modes

  • coupling systems through hidden globals or timing assumptions
  • writing logic that is hard to test or debug
  • optimizing the wrong layer before measuring

Related Agents

  • build-engineer
  • release-manager
  • qa-lead

Related Commands

  • release-check
  • verify
  • plan

Notes

  • Keep this skill aligned with the relevant rules layer and current project documentation.
  • If engine-specific constraints materially change the workflow, hand off to the matching engine skill or engine-specific reviewer.

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