CI Test Pipeline Optimization

When to Use

• Use this skill when you need evidence-bounded analysis, design, or validation preparation for pipeline stages, feedback latency, resources, flakiness, caching/sharding, and rollback boundaries.
• Use it to review a plan, result, or metric and turn the review into executable improvements.
• Use it when input is incomplete but a bounded first pass with assumptions, gaps, and human-decision boundaries is still useful.

Output Format Options

• Default to Markdown organized by domain risk, evidence state, priority, and boundary.
• When the user requests tables, CSV, JSON, or ticket fields, preserve the same finding fields, evidence, and decision boundaries.
• Before machine consumption, confirm the schema, enums, required fields, and evidence sources.
• In Markdown tables, escape literal | characters inside cells as \| (including inline code), or rephrase them so they do not create extra columns.

How to Use