check
Run CIAgent regression checks after changing an AI agent's code, prompts, or knowledge base in a repo that has agentci_spec.yaml, and interpret the results. Use after editing agent logic, before committing agent changes, or when the user asks whether the agent still works.
npx skills add davepoon/buildwithclaude --skill check --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Run CIAgent checks on this repo's agent The repo has `agentci_spec.yaml` (if it does not, use the `onboard` skill instead). Your job: run the right check for the change that was just made, read the result correctly, and never paper over a failure. ## Which command | Situation | Command | |---|---| | Spec or wiring changed, or no API keys | `ciagent test --mock` | | Agent code / prompt / retrieva
What does the check skill do?
Run CIAgent regression checks after changing an AI agent's code, prompts, or knowledge base in a repo that has agentci_spec.yaml, and interpret the results. Use after editing agent logic, before committing agent changes, or when the user asks whether the agent still works.
How do I install it?
Run `npx skills add davepoon/buildwithclaude --skill check --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From davepoon/buildwithclaude, a repository with 3,251 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.