What problem does it solve? CI pipelines often exist but fail to act as a real quality gate: they run stages in the wrong order, waste time on expensive tests before cheap checks, or report a green status that means nothing. This Skill designs a new pipeline or audits an existing one so it fails early, for the right reason, and produces a trustworthy per-SHA status that release processes can consume. ## Core Features & Use Cases - Ordered stage design: Structures eight stages by increasing cost — lint/format, type check, unit tests, integration tests, E2E, security scanning, build, and artifacts — cutting the pipeline at the first failure. - Existing pipeline audit: Reads the current CI configuration before proposing changes, detecting the stack and runner (GitHub Actions by default) and removing decorative stages. - Release integration: Ensures the pipeline reports a per-SHA status that a release gate can read as ci_green, while explicitly excluding deployment, which belongs to the release workflow. - Use Case: A team adopting GitHub Actions asks for a pipeline review; the Skill inspects the existing YAML, reorders stages so lint and type checks run before E2E, adds secret scanning and reproducible artifact checksums, and confirms the status check feeds the release gate. ## Quick Start Ask the assistant to run /ci to design or audit the CI pipeline for this repository.