wachterjohanneswachterjohannes/symfony-skills/skills/make-ci/SKILL.md

make-ci

Skill4 starsChanged 2 months agoMITView on GitHub

Use when a project needs a CI pipeline or workflow for GitHub Actions or GitLab CI, such as running tests and linters on every push or pull request.

Reads credentials

In this repository24 other files it gives its agents.
- AGENTS.mdAGENTS.md
- cli-conventionsSkill
- componentsSkill
- configurationSkill
- discoverSkill
- make-commandSkill
- make-controllerSkill
- make-crudSkill
- make-decoratorSkill
- make-entitySkill
- make-formSkill
- make-listenerSkill
- make-migrationSkill
- make-registration-formSkill
- make-reset-passwordSkill
- make-security-customSkill
- make-security-form-loginSkill
- make-testSkill
- make-twig-extensionSkill
- make-userSkill
- make-voterSkill
- make-webhookSkill
- servicesSkill
- templatesSkill

The file

We split this skill into the rules it gives an agent

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

≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
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

Distinctive:
Test, PHP CS Fixer, Twig CS Fixer and PHPStan jobs exist only when the project has the tool.
line 35
Very specific:
Only the exact target paths are protected: the maker refuses to overwrite .github/workflows/ci.yaml and .gitlab-ci.yml, nothing else.
line 40

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

CI configuration

symfony console make:ci --platform=github-actions --php-version=8.4

--platform takes github-actions or gitlab-ci and is required non-interactively. The maker detects the rest: installed tools from composer.json, translation formats from translations/, the default branch from git, and the database engine from DATABASE_URL in .env. Two detections deserve overriding as a rule, not an exception:

--php-version (format major.minor). The detection takes the first version in the php constraint of composer.json, so >=8.2 yields 8.2 even when production runs 8.4. Pass the real version.
--branch. The detection only works in a clone with a remote. A fresh repository silently falls back to main.

--database takes postgres, mysql, mariadb, sqlite or none and only has an effect when Doctrine is installed. A missing or non-standard DATABASE_URL silently falls back to postgres, so pass the option whenever the DSN is unusual.

What you get

.github/workflows/ci.yaml, plus a dependabot.yml for composer and github-actions updates when none exists. For GitLab, .gitlab-ci.yml. The lint job is always there. Test, PHP CS Fixer, Twig CS Fixer and PHPStan jobs exist only when the project has the tool.

What is yours

Only the exact target paths are protected: the maker refuses to overwrite .github/workflows/ci.yaml and .gitlab-ci.yml, nothing else. A project with CI under another file name gets a second, parallel workflow. Check what exists before running.
The actions are pinned by SHA with the version as a comment. Keep them pinned. Do not simplify a pin to a tag.
Project-specific steps such as deployments, coverage uploads or custom composer scripts are yours to add. A tool that lives outside composer.json, in a tools/ directory or as a phar, gets no job either. Add it by hand.

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