Findings agents act on
Every finding carries three separate fields. What is wrong, the standard, and the next action, so agents act on the fix without parsing prose.
See a finding
Deterministic, actionable checks for the standards your prompts stop enforcing. Every finding tells the agent what is wrong, what was expected, and how to fix it.
The gate wizard configures Biome, knip, dependency-cruiser, and Vibator in one guided run. It shows every change as a diff before applying it, and it never overwrites a config you already have.
$ npm create @vibator/gate$ pnpm create @vibator/gate$ yarn create @vibator/gate$ bun create @vibator/gatePrefer to start smaller? Add Vibator on its own.
Linters print a rule id and leave the rest to you. Vibator states the problem, the standard, and the fix as separate fields, so a human reads a sentence and an agent executes a step:
{
"file": "src/components/editor.tsx",
"line": 401,
"message": "\"data\" is a filler name that says nothing about the value",
"expected": "A name stating what the value is",
"fix": "Rename it after what it holds, such as the entity or unit",
"docs": [{ "absolutePath": "…/vibator/docs/rules/meaningful-names.md" }]
}