Skip to main content

Video transcript

Kiro CLI demo: investigating a slow CI job

In a terminal at ~/work/fastify, the user runs 'kiro-cli chat' and the Kiro CLI V3 welcome banner appears, with a status line showing the Default agent, the auto model, context use and the git branch main. Waits where only a spinner moved are shortened. The user types 'CI unit tests are our slowest check. Time them and shard ci.yml to fix it.' Kiro runs shell commands to read package.json, the CI workflow and the borp test runner config, uses the gh CLI to pull job and step timings from recent successful CI runs, and times the full suite locally (2401 tests in about 15 seconds). Kiro answers that it hasn't edited ci.yml: sharding wouldn't fix this because the tests aren't what's slow. The whole CI run takes 466 to 533 seconds, the test step 36 to 56 seconds, and npm install 57 to 79 seconds, while test-unit can't start until lint and the coverage jobs finish. Sharding would save about 30 seconds per job and take the unit matrix from 6 jobs to 12 to 18, and borp has no shard option. Kiro suggests removing coverage-nix and coverage-win from test-unit's needs, a one-line change that should cut 120 to 200 seconds, notes the trade-off, and asks 'Should I make the needs change?' The prompt returns with the turn's credits (1.18) and time (1m 35s).

← Return to Home