about
Repeated judgment, compiled.
Coldworks runs agent workflows and compiles the judgments they keep repeating into deterministic, guarded code that you own.
The first case
Most pull requests don’t need a human.
Coldworks reviews your pull requests, remembers what your team decided, and turns the judgments it keeps repeating into checks you own.
Every pull request gets a verdict: cleared, or needs a reader. Coldworks routes attention. It never blocks a merge, never writes code, and publishes its own miss rate.
Judgments that come back the same every time become guarded, tested checks. A maintainer signs each one, and it runs first in your CI.
Three rules, in writing
Route, never block.
The PR proceeds either way. Coldworks only decides who has to look. Tools that block get disabled.
Never write code, never open a PR.
The moment it authors, it owns the authorship.
Publish the miss rate.
Every quarter, including the incidents that came from PRs it cleared. A gate that never publishes its errors is a marketing claim; one that does can survive being wrong. The scoreboard is live; the miss-rate number is not yet.
Get involved
Two ways in.
01
Star it
Coldworks reviews its own pull requests on this repository. A star is the cheapest way to say the live path is worth hardening for other installs.
02
Tell us your story
Had a PR that needed a human and didn’t get one? Or one Coldworks would have wrongly flagged? Open it as an issue — it’s the fastest way to argue with the scoring.
Open an issue