ci-optimize

Optimize CI Pipeline

Improve CI/CD pipeline performance by analyzing and optimizing caching, parallelization, and job structure.

Input Parsing

Parse $ARGUMENTS to extract path and optional focus areas:

Format: [path] [-- <focus-areas>]

Examples:
- /acc:ci-optimize
- /acc:ci-optimize ./
- /acc:ci-optimize -- focus on caching
- /acc:ci-optimize ./ -- reduce Docker build time
- /acc:ci-optimize -- parallelize tests, optimize lint

Parsing rules:

1. Split $ARGUMENTS by -- (space-dash-dash-space)
2. First part = positional arguments, Second part = meta-instructions (focus areas)
3. In positional arguments, extract path (optional, defaults to ./)
4. After -- = focus areas (optional optimization targets)
5. If no path provided, default to current directory (./)
6. Validate path exists before proceeding

Pre-flight Check

1. Find CI configuration:

   ls .github/workflows/*.yml 2>/dev/null
   ls .gitlab-ci.yml 2>/dev/null
   

2. If no CI found:

   • Suggest running /acc:ci-setup first

3. Check for optimization targets:

   # Check for caching
   grep -r "cache" .github/workflows/ .gitlab-ci.yml 2>/dev/null
   
   # Check job dependencies
   grep -rE "(needs:|depends_on:)" .github/workflows/ .gitlab-ci.yml 2>/dev/null
   
   # Check for Docker
   ls Dockerfile* 2>/dev/null
   

Instructions

Use the acc:ci-coordinator agent to optimize:

Task tool with subagent_type="acc:ci-coordinator"
prompt: "Optimize CI pipeline at [PATH].

Operation: OPTIMIZE

[FOCUS_AREAS if provided]

Analysis targets:
1. Caching efficiency
2. Job parallelization
3. Dependency structure
4. Docker build optimization
5. Resource usage

Provide:
- Current vs optimized comparison
- Specific changes to make
- Estimated time savings"

Expected Output

The coordinator will:

1. Analyze current pipeline:

   • Total execution time
   • Critical path
   • Parallelism percentage
   • Cache hit rates

2. Identify bottlenecks:

   • Slowest jobs
   • Sequential when parallel possible
   • Cache misses
   • Unnecessary waits