Fixing Vibator Findings
Act on vibator findings: consume the JSON report, apply each finding's fix, read the guideline behind a rule when the fix is not obvious, verify with a re-run, and use a reasoned ignore only when the rule is genuinely wrong. Use when a vibator run fails, when asked to clean up quality-gate findings, or before declaring work done in a repo that has a vibator.json.
Writing Vibator Rules
Author a custom vibator quality-gate rule: the rule contract, file vs project scope, diagnostics, options, guideline document, registration and tests. Use when adding a project-specific lint or guardrail, when a standard keeps coming up in code review and should be enforced automatically, or when asked to write, debug or publish a vibator rule or plugin.
Configuring Vibator
Set up or tune vibator.json for a project: discover what the project has (locales, env files, tsconfigs, generators), enable and configure the rules that fit, wire project guidelines onto rules, and tune severities without weakening the gate. Use when asked to add vibator to a project, configure or adjust its quality gates, enable a specific rule, or when a vibator run fails because a rule is mis…