CI Pipeline Design skill for Claude and Codex
A CI pipeline redesign that fails fast, runs in parallel where it safely can, caches well, and quarantines flaky tests, with a target total runtime and a list…
Install it once and Claude or Codex runs it for you. When your request matches, your AI loads the skill, asks for anything it is missing, and works through the template itself. Prefer to fill it in by hand? See the full prompt template.
Download the skill (.zip) · View SKILL.md
When it is used
Use when a CI pipeline is slow, flaky, or expensive and needs its stages reordered, parallelised, cached, and trimmed to a target runtime. Do not use for writing deployment or release automation, or fixing one failing build. Related topics: Engineering, Technical, Productivity.
What it will ask you for
- Project (longer free text)
- Pipeline today (longer free text)
- Test suite (longer free text)
- Platform (choose one: GitHub Actions, GitLab CI, CircleCI, Jenkins, Buildkite)
- Team size and commits per day (free text, e.g. "Both")
- What hurts (choose any: Too slow, Flaky tests, Unclear failures, Expensive, Blocks releases)
How it works
- Order the stages so the cheapest checks fail first and slow end-to-end tests run last.
- Mark which stages can run in parallel and which depend on another stage, with the reason for each dependency.
- Define a cache for dependencies and build artefacts with a key that invalidates only when its inputs change.
- Split the commit-blocking checks from main-only and nightly jobs, and quarantine flaky tests rather than retrying them.
- Set a target runtime for the blocking path and list the exact steps to cut or move to reach it.
What you get
A stage table with columns stage, runs when, parallel with, cache, and expected time, then a config skeleton for the chosen platform and a numbered list of cuts to reach the target runtime.
What it watches out for
- Adding blanket retries to hide flaky tests, which doubles runtime and lets real failures slip through.
- Using a cache key that never changes, so stale dependencies are served after a lockfile update.
- Parallelising stages that share a build artefact, so jobs race and fail intermittently.
How to install
Claude.ai and the Claude desktop app
- Download the skill .zip.
- Open Settings, then Capabilities, and find Skills.
- Choose Upload skill and select the .zip.
- Ask Claude for help with the task. It loads the skill when your request matches.
Claude Code
- Download the skill .zip.
- Unzip it into ~/.claude/skills/ (or .claude/skills/ inside a project).
- Start a new session. Claude Code loads the skill when your request matches.
Codex
- Download the skill .zip.
- Unzip it into ~/.agents/skills/ (or .agents/skills/ inside a project).
- Codex picks it up on its own. Type $ and the skill name to use it, or just ask for the task.
Cursor
- Download the Cursor rule (.mdc).
- Save it in .cursor/rules/ inside your project.
- Cursor's agent applies the rule when your request matches its description.
AGENTS.md (Codex, Cursor, and other coding agents)
- Copy the AGENTS.md section.
- Paste it into AGENTS.md at the root of your repository, creating the file if needed.
- Coding agents that read AGENTS.md follow it when your request fits.