CI Kit
Run your CI on your laptop, before you push.
CI Kit gives a repository a local gate that mirrors what the GitHub Actions workflows do: the same installs, the same linters, the same type checks, the same tests. It also runs the workflow files themselves locally through act, so the YAML can be checked without waiting for a runner. The design principle is a single copy of the setup: the gate scripts live in the repository under scripts/ci/, and both the Makefile and the workflow call them. There is one copy of the setup, so it cannot disagree with itself. The tool works with any language — the gates are driven by what the repository actually contains — and it deliberately does not take over your pipeline. The workflows stay the source of truth; the kit makes them cheap to try.
A feedback guarantee that a billing decision cannot switch off
On 21 October 2026 the largest repository in the workspace had 28 failing runs out of the last 30, none of which failed on code — GitHub had refused to start the jobs because of a spending limit. Every run failed in about six seconds. The local gate answers the same question in about a hundred seconds, and it says why.
Three real defects found in under four minutes, without a runner
A stale secret-scan allowlist entry that was failing the CI scan on a tracked documentation file, ninety-three dependency advisories of which eight were critical, and build artefacts tripping a working-tree secret scan. The first two were masked because CI was red for a completely different reason, and nobody could tell the two apart.
The claim is deliberately narrower than the marketing would be
The evidence document has a section titled 'What is not claimed'. It states plainly that the local gate is not faster than a runner, that no runner-minute savings are claimed, and that the numbers come from one machine and one workspace. The value of the tool is a guarantee of feedback, not a speedup — and the documentation says so before anyone asks.