msft-tkendrick/ci-cd-optimizer
Find and fix slow, wasteful, or risky CI/CD setup (caching, hermetic builds, container layers, GitHub Packages, workflow structure) with the CI/CD Optimizer linter and run reports, read-only.
Explain why a GitHub Actions workflow run was slow, using the CI/CD Optimizer's run telemetry, critical path, and Gantt report. Use when the user shares a workflow run URL or id, asks why CI took so long, wants to know which job or step is the bottleneck, or wants to compare a run with its recent baseline.
Speed up a repository's CI/CD with the CI/CD Optimizer linter. Use when asked to make builds, tests, or releases faster or cheaper, to review GitHub Actions workflows, Dockerfiles, or package setup for caching, hermetic builds, container layers, GitHub Packages (ghcr.io, npm.pkg.github.com), concurrency, or affected-only testing, or to prepare a repo for frequent agent-driven pull requests.
Triage CI/CD Optimizer findings into fix now, fix later, or accept, and write precise suppressions with reasons. Use when a cicd-lint or CI/CD Optimizer check reports warnings or errors on a pull request, when the user asks whether a finding matters, or when a finding should be silenced deliberately instead of fixed.