domains / families / software-engineering / 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. Confirm a change before merge. `/check verify` drives the real app to prove behavior against the spec (every acceptance criterion met, every surface built). `/check review` runs a senior code review on a fresh model, one that did not write the code. Verify after /develop, review before a PR. Writes to docs/reviews/, never edits code.
The two skills share the name 'check' and the high-level goal of verifying work before it is finalized, but they define completely different procedures, tools, and outputs. The first is a domain-specific skill for running 'CIAgent' regression tests on AI agent code using a specific CLI and interpreting JSON results. The second is a general-purpose software engineering skill that routes to either a runtime verification mode (driving the app) or a code review mode (using a different LLM). They do not overlap in steps or constraints; one is a specific tool wrapper, the other is a workflow orchestrator. Combining them is necessary to preserve both distinct verification strategies.