create-ci-skill
Create a CI skill
GoodFlows is the check. This skill reads goodflows.toml or .goodflows.toml and writes a project-local skill (run-ci-<app>/) that runs those jobs with the goodflows CLI. The next agent reads it cold, mid-task, without having seen the repo.
Do not open any other CI system and do not mention one in the generated skill. Do not turn a Makefile, a package script, a hook, or a workflow file into jobs. GoodFlows is not a layer on top of another runner.
Write that skill in the directory the harness you are running in loads. Decide from the harness, not from which dot-directories the repo already contains:
- Amp, Cursor, OpenCode, Codex, and T3 Code:
.agents/skills/run-ci-<app>/ - Claude Code:
.claude/skills/run-ci-<app>/ - Grok CLI:
.grok/skills/run-ci-<app>/
If the harness is unknown, use .agents/skills/run-ci-<app>/. Write one directory. Every file below is inside it.
<app> is a slug of the repository name (git remote get-url origin, else the checkout directory): lowercase, every character outside a-z, 0-9, and - replaced with -, repeats collapsed, ends trimmed. One invocation writes one skill.
1. Read the config
Look only for a GoodFlows config. The CLI uses the first of goodflows.toml and .goodflows.toml that exists in the current directory, unless a command passes --config. Read that file and no other CI file.