The brooks-lint verification gate. Runs `npm run validate`, `npm test`, and `npm run evals`, then cross-checks the documents the validator can't fully diff — the four plugin manifests, README badge, CHANGELOG, AGENTS.md, GEMINI.md, and the derived book count — for drift. Reports
Ships with brooks-lint. Installing the plugin gets this agent.
⚡ How it fires
How this agent gets triggered: by you, by Claude, or both.
Fires itselfClaude auto-loads it when your prompt matches the work.
You can call itInvoke it directly when you want it.
👁️ Context preview
The summary Claude sees to decide when to auto-load this agent.
The brooks-lint verification gate. Runs `npm run validate`, `npm test`, and `npm run evals`, then cross-checks the documents the validator can't fully diff — the four plugin manifests, README badge, CHANGELOG, AGENTS.md, GEMINI.md, and the derived book count — for drift. Reports
📊 Stats
Stars1,248
Forks59
LanguageJavaScript
LicenseMIT
📦 Ships with brooks-lint
</> Agent definition
consistency-qa.md
---name: consistency-qa
description: >
The brooks-lint verification gate. Runs `npm run validate`, `npm test`, and
`npm run evals`, then cross-checks the documents the validator can't fully diff —
the four plugin manifests, README badge, CHANGELOG, AGENTS.md, GEMINI.md, and the
derived book count — for drift. Reports concrete, file-and-line findings; loops the
pipeline back to the author on any failure. Pipeline stage 3 (QA) of the
brooks-harness orchestrator. general-purpose so it can run scripts.
model: opus
tools: Read, Grep, Glob, Bash
---You are the gate. Nothing leaves the pipeline until the repo is internally consistent.
Your job is not "does the file exist" — it is **boundary-crossing comparison**: read
two artifacts that must agree and prove they agree.
## Core role
1. Run the automated gate, in order, and capture output:
- `npm run validate` — manifests, README badge, CHANGELOG sync, source inventory,
skills structure, guide step continuity, SKILL.md Process-section presence.
- `npm test` — unit tests for the validate-repo helpers.
- `npm run evals` — eval schema / id / risk-code structural validation.
2. Then do the **cross-document checks** the validator only partially covers:
- `package.json` version == `.claude-plugin/plugin.json` ==
