agentleFS
aprameyakaprameyak/coding-skills/setup-ci/SKILL.md

setup-ci

Skill1 starsChanged 41 days agoMITView on GitHub

Design and add CI/CD pipelines with useful quality gates. Use when creating or changing GitHub Actions, build pipelines, or deploy workflows.

6 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

6 rules. 0 are common, 5 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 5 edited versions we read keep these.

  • 5

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Keep feedback loops short.

    line 13
  2. Distinctive:

    Prefer reusable workflows/templates already in the org/repo.

    line 14
  3. Distinctive:

    Add caching and artifact upload only where useful.

    line 21
  4. Distinctive:

    Document required secrets and how to run the same checks locally.

    line 22
  5. Very specific:

    No broad write permissions by default

    line 26
  6. Distinctive:

    No publishing/deploy from fork PRs without controls

    line 27

“Common” is measured: kept by at least 6 in 10 of the 5 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

Setup CI

Principles

  • Shift checks left: format/lint/typecheck/unit on every PR.
  • Fail fast with clear logs; cache dependencies.
  • Pin action versions; least-privilege permissions.
  • Keep feedback loops short; reserve slow jobs for needed paths.
  • Prefer reusable workflows/templates already in the org/repo.

Process

  1. Detect existing CI and package scripts.
  2. Define gates: install → lint/typecheck → test → build → (optional) deploy.
  3. Match local developer commands to CI commands.
  4. Add caching and artifact upload only where useful.
  5. Document required secrets and how to run the same checks locally.

Safety

  • No broad write permissions by default
  • No publishing/deploy from fork PRs without controls
  • Secrets never echoed

Exit

  • Pipeline runs on the target events
  • Failure messages point to the real command
  • Local reproduction command documented

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.