---

name: optimize-cicd-pipeline description: Analyzes CI/CD pipelines to identify common antipatterns (like slow feedback loops or sequential steps) and recommends best practice patterns (like build images, parallelization, and build-once-deploy-anywhere). Use when designing, auditing, or troubleshooting CI/CD workflows to improve speed and reliability.

Optimize CI/CD Pipeline

This skill provides a framework for auditing and improving CI/CD pipelines. The primary goal of any pipeline optimization is to shorten the feedback loop. The faster a developer knows something is wrong, the cheaper it is to fix.

Usage Instructions

When analyzing a pipeline configuration or advising on DevOps practices, compare the user's current setup against the Antipatterns below. If an antipattern is detected, recommend the corresponding Pattern.

1. Core Philosophy Checklist

• Feedback Loop: Is the time from "commit" to "failure notification" under 10 minutes?
• Reproducibility: Can a developer run the exact same build command locally?
• Maintenance: Is the pipeline treated as a software product (versioned, refactored, maintained)?

2. Pattern Analysis

Use this table to diagnose issues and prescribe solutions:

Common Recommendations

1. Target Time: If a pipeline takes >15 minutes, productivity drops due to context switching. Aggressively optimize parallelization.
2. Environment Consistency: Never allow the CI server environment to drift from the developer's local environment.
3. Drafting Pipelines: Always start by defining the "Happy Path" (success state), then add the necessary gates to protect it.