Automated Check
Pemeriksaan Otomatis
A deterministic verification that runs in the environment: tests, type checks, lints, build. Pass or fail, no judgement.
An automated check is a deterministic verification that runs in the environment: a test suite, a type checker, a linter, a build. It produces a pass or fail, and it applies the same rule every time, which is what makes it trustworthy.
This is where AI-assisted work pays for itself. Generated code is plausible rather than correct, and a check is the cheapest possible way to find out which one you got. Every check that exists and passes is a class of mistake the agent cannot make unnoticed.
The limits are the same as any test suite. A check only covers the cases someone thought of, and an agent writing both the code and the checks will cover the cases it understood and skip the ones it misunderstood. Keep some checks written by people, and keep the integration tests that run the real thing rather than a mock of it.
Related terms
Testing
The cheapest way to know a change is safe: a check that runs without a human reading anything.
Evaluation
Measuring whether the system does the job, on a fixed set of cases, repeatedly.
Automated Review
An agent reviewing another agent's work, often with a different model or system prompt. It forms a judgement.
Human Review
The user reading the code the agent produced and forming a judgement on it. Reading the diff counts; reading the summary does not.
Regression
A change that made something worse. The reason to keep tests at all.
Want this working inside your team?
It starts with one conversation about your workflow.