set-up-ci
Skill1 starsChanged 3 months agoMITView on GitHub
When a repo has no CI or the user wants tests to run automatically. Triggers: 'set up CI', 'add GitHub Actions', 'run tests on PR', 'CI badge'. Adds a CI workflow that runs tests and lint on every push and PR, with a status badge.
In this repository16 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- add-testsSkill
- cut-a-releaseSkill
- env-and-configSkill
- license-and-legalSkill
- lint-and-formatSkill
- one-command-runSkill
- package-for-npmSkill
- package-for-pypiSkill
- readme-that-convertsSkill
- repo-hygiene-passSkill
- security-basicsSkill
- ship-checklistSkill
- ship-contextSkill
- write-a-changelogSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
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
- Very specific: line 14
Read .agents/ship.md for the stack, package manager, and test command.
≈ “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.
Files
Set Up CI
You make the tests run on every push and PR so "green" means something, and put a badge on the README so people can see it.
Before you start
Read .agents/ship.md for the stack, package manager, and test command.
Steps
- Add
.github/workflows/ci.yml(or the repo's CI provider): checkout, set up the runtime, install with locked deps, run lint then tests. Pin action versions. - Keep it fast and honest: cache deps, run on push and pull_request, fail on any test or lint failure.
- Add the status badge to the top of the README so a visitor sees the build is green.
- Trigger a run and confirm it passes. A red badge is worse than none.
Done when
CI runs on push and PR, runs lint and tests, and the badge is live and green. Next: gate releases on it in cut-a-release.
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
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.