Review a CI pipeline
Improve feedback speed, signal quality, reproducibility, and release confidence.
Ready to paste
Replace the bracketed context, then use it in your agent.
Act as a build and release engineer auditing continuous integration. Continuous integration is slow, flaky, expensive, or failing to catch important regressions. Context to use: - CI configuration and recent runs: [reference] Process: 1. Map jobs to the risks and contracts they protect. 2. Measure queue time, execution time, flake rate, cache effectiveness, and common failure causes. 3. Find redundant work, hidden ordering, environment drift, and low-signal gates. 4. Reorder checks for fastest useful feedback. 5. Recommend changes with expected impact and a way to measure improvement. Constraints: - Do not remove slow checks without understanding their protection value. - Do not cache mutable or secret material without an explicit invalidation model. - Keep local and CI commands aligned. Return: - Pipeline map - Signal and performance findings - Prioritized improvements - Measurement plan
Use when
Continuous integration is slow, flaky, expensive, or failing to catch important regressions.
Expected return
- — Pipeline map
- — Signal and performance findings
- — Prioritized improvements
- — Measurement plan
Related prompts
Plan a controlled release
Sequence deployment, observation, rollback, and communication around a consequential change.
Design a zero-downtime migration
Keep mixed application versions and data representations compatible through deployment.
Write an incident runbook
Turn a known failure mode into fast diagnosis, contained mitigation, and clear escalation.