ci

Designs or audits CI pipelines covering lint, tests, security, build, and artifacts.

Updated Sep 17, 2026
One-click install
npx skills add https://github.com/karenrebecag/spec-driven-standards --skill ci-karenrebecag
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ci
Source: https://github.com/karenrebecag/spec-driven-standards/tree/main/plugins/delivery/skills/ci
Command: npx skills add https://github.com/karenrebecag/spec-driven-standards --skill ci-karenrebecag

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about ci

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I design a CI pipeline that fails fast?

Order stages by increasing cost: lint and format first, then type check, unit tests, integration tests, E2E, security scans, build, and artifacts. Stop the pipeline at the first failing stage so cheap checks gate expensive ones.

What stages should a CI pipeline include?

A complete pipeline covers lint/format, type checking, unit tests, integration tests with mocked or ephemeral dependencies, critical E2E flows, security checks like npm audit and secret scanning, production build, and versioned reproducible artifacts.

How many E2E tests should run in CI?

Only critical user flows should run as E2E tests in CI, typically with Playwright. E2E tests are expensive and fragile, so covering everything end-to-end slows the pipeline and creates flaky failures.

Should CI pipelines include automatic deployment?

No. This Skill deliberately excludes deployment from the pipeline; deployment belongs to a separate release workflow with its own gate. CI should only report a per-SHA status that the release process reads as ci_green.

Does this work with GitHub Actions?

Yes. GitHub Actions is the default runner assumed, though the Skill detects the actual stack and runner in the repository first and reads the existing configuration before proposing changes.