CatalogueDelivery & Operations
CI/CD Pipeline Maturity Audit
Reads the pipeline for whether a change can be built, checked, and released the same way every time.
What it examines
- Build and test stages a change must pass
- Who can deploy, and whether that path is the only path
- Whether a failed release can be rolled back
- Secrets and manual steps hiding inside the pipeline
What you get back
A findings file. Each item has the evidence, how serious it is, and a fix.
Dependencies
- An AI coding agent that reads SKILL.md files, such as Claude Code, Codex or Gemini CLI
- Read access to the repository, including pipeline definitions, deploy scripts and any deployment runbooks
- Git history, for merge and tag timestamps used to calculate lead time
- Python 3.11 or newer with the jsonschema package, to check findings.json before fixing anything
- Optional: CI run history from the API or web UI. Without it, lead time is only an estimate from tags and the changelog, and is labelled that way.
- Optional: a trustworthy E4 finding set. The remediate skill needs it before it goes past a plan.
How it works
The audit is read-only. It runs seven checks: pipeline step classification, deploy lead time, the state of the rollback path (exercised, documented only or absent), environment parity, the value of manual approvals, build reproducibility and pipeline secret handling.
It never triggers a deployment, runs a pipeline against a live environment or rotates a secret. Missing inputs become insufficient-evidence entries, never silent skips.
The remediate skill reads findings.json only. It adds or strengthens automated tests first, proves a rollback path in non-production before touching production, and changes one stage at a time.
Setup
- Unzip the download, then copy the audit and remediate folders into your agent's skills folder (for Claude Code, .claude/skills/) in the repository you want to check.
- Gather the access listed under Dependencies, and decide which environments count as production.
- Ask your agent: Run a CI/CD pipeline maturity audit on [scope]. What counts as production: [environments]. Mode: audit only.
- Check the result with the validator: pip install jsonschema, then python3 schema/validate.py findings.json.
- Read findings.md. Once you have reviewed the findings, run the remediate skill using findings.json, or re-run with Mode: audit and remediate.
Run it with your agent
Copy the prompt, fill in the parts in square brackets, and paste it into your agent.
Run the e1-cicd-pipeline-maturity-audit skill on this repository. What counts as production: [environments]. CI run history: [available, or not]. Mode: audit only. Do not change any code. Write findings.json and findings.md in the repository root.
Run the e1-cicd-pipeline-maturity-remediate skill using findings.json. Work through the findings I choose, and leave the rest open.