CI Optimization

Coming (phase 6)

Years of CI waste nobody has time to find

CI/CD pipeline optimization from your own history: where your CI loses time and money, a ready-to-paste fix for your coding agent, and the result measured.

Find what your CI is wasting

Illustrative. The workflows, figures and prompt in it are examples.

From years of runs to a faster pipeline.

  1. Your CI history comes in

    It reads your repository's CI history, its workflow configuration and its structure.

  2. The bottlenecks light up

    It maps each one to what OhMako offers, such as snapshots, warm pools, machine sizes, parallelism and caching, with its evidence, estimated savings, effort and confidence.

  3. It writes the prompt

    It writes a ready-to-paste prompt for your coding agent: what to change, where, and why.

  4. Your agent applies it

    Your coding agent makes the change and opens a pull request. Nothing changes until you merge it.

  5. Before and after

    Once the pull request lands, it benchmarks the runs after it against the runs before.

  6. A later regression is caught

    It keeps watching, and catches a regression against its baseline: in the weekly summary, or the same day as an anomaly.

How it works

Read-only by default.

By default it only reads: your CI history, workflow configuration and repository structure. The fix comes as a prompt for your coding agent, so a change reaches you as a pull request. It covers GitHub Actions and GitLab CI.

The skill

Start with the free skill.

The CI Optimization skill is free and open source, works in the coding agent you already use, and gives useful advice without an OhMako account.

Connect the OhMako MCP server and it reads your OhMako jobs, logs and spend too: what ohmako runner and ohmako usage show at a terminal.

Continuous CI intelligence

It keeps watching.

Scheduled reports

Anomalies daily, a summary weekly and trends monthly.

What they cover

Cost, duration, queue time, cache and snapshot efficiency, failures, retries and utilization.

Regressions caught

Each measure has a baseline, and the history says what saved how much and what regressed.

Where you read them

In the dashboard, by email, in Slack, or on GitHub and GitLab.

Price

The skill is free.

Where an analysis uses AI, it's billed at cost plus 20%.

Join the invite list

Tell us which products you want first. Invites go out in waves, product by product.

Find what your CI is wasting