maintain-ci-skill
Maintain a CI skill
A run-ci-<app> skill goes stale when the GoodFlows config changes. This skill is the upkeep pass for a skill written by create-ci-skill. It keeps the scenario answers already in that file, and it edits the file only where a workflow, job, goodflows command, or failure note no longer matches the config.
It does not generate a skill. No run-ci-<app> directory means stop.
Do not open any other CI system and do not mention one, in this run or in the skill. Do not turn a Makefile, a package script, a hook, or a workflow file into jobs.
Outcomes
Pick one, and say which:
- unchanged — the skill already matches the config. No questions. No file write.
- updated — the skill was edited so every command and job name matches the config, then the
goodflowssteps were run once. Each step is pass, fail, or blocked. - stopped — there is no
run-ci-<app>skill, or there is no GoodFlows config. Nothing was written.
Edit scope
Edit only the chosen run-ci-<app> directory (its SKILL.md and a helper script that directory already owns). Do not edit product code. Do not edit goodflows.toml or .goodflows.toml unless the user explicitly says to apply a proposal you showed them in this run.