agentleFS
PradnyeshpPradnyeshp/Claude-Skills/.claude/skills/ci-setup/SKILL.md

ci-setup

Skill2 starsChanged 4 months agoMITView on GitHub

Generate or improve a CI pipeline (GitHub Actions by default) that installs, lints, tests, and builds the project, matching its language and tooling. Use when the user says "set up CI", "add GitHub Actions", "write a CI pipeline", "add a test workflow", or "automate my builds".

2 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

4 rules. About 0 are common, 2 are distinctive, and 2 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.

  • 2

    Very specific

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

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

    Detect the stack and its real commands: Read the manifest/scripts above to find the actual install, lint, test, and build commands — use …

    line 23
  2. Distinctive:

    Don't duplicate existing workflows: If CI already exists, read it and propose targeted additions/fixes.

    line 28
  3. Very specific:

    Write the file to the conventional path (.github/workflows/ci.yml, .gitlab-ci.yml, etc.).

    line 29
  4. Distinctive:

    After writing, summarize what each job does and note anything the user must configure (secrets, branch protection, required status checks).

    line 30

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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

Project + existing CI detection

!ls package.json pyproject.toml requirements.txt Cargo.toml go.mod pom.xml build.gradle Gemfile 2>/dev/null

!ls -d .github/workflows .gitlab-ci.yml .circleci 2>/dev/null && echo "(existing CI config above — extend it, don't duplicate)"

!cat package.json 2>/dev/null | grep -A20 '"scripts"'

Instructions

Generate or improve a CI pipeline for this project (use the provider/jobs in $ARGUMENTS if given; otherwise default to GitHub Actions).

Rules

  1. Detect the stack and its real commands. Read the manifest/scripts above to find the actual install, lint, test, and build commands — use those verbatim (e.g. npm ci + npm test, pytest, cargo test, go test ./...). Don't invent script names.
  2. Pin versions sensibly. Pin action versions (e.g. actions/checkout@v4) and the language runtime to what the project targets. Use a matrix only when the project genuinely supports multiple versions.
  3. Standard job order: checkout → set up runtime → restore cache → install → lint → test → build. Cache the dependency directory (npm/pip/cargo/go module cache) keyed on the lockfile hash.
  4. Trigger on push to the default branch and on pull requests, unless the user specifies otherwise.
  5. Keep it minimal and fast. Fail early (lint before test), run independent jobs in parallel, and don't add deploy steps, secrets, or external integrations unless asked — flag where they'd plug in instead.
  6. Don't duplicate existing workflows. If CI already exists, read it and propose targeted additions/fixes.
  7. Write the file to the conventional path (.github/workflows/ci.yml, .gitlab-ci.yml, etc.).
  8. After writing, summarize what each job does and note anything the user must configure (secrets, branch protection, required status checks).

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.