brooks-harness
Maintenance orchestrator for the brooks-lint plugin itself. Runs a sequential subagent pipeline — author → eval → QA → trigger-audit → release — to add or edit a skill, refresh the eval suite, keep the four manifests + all README translations + CHANGELOG + AGENTS/GEMINI in sync, audit trigger boundaries, and cut releases. Drives the five agents in .claude/agents/ (skill-author, eval-curator, consistency-qa, trigger-boundary-auditor, release-manager). Triggers when the maintainer asks to work ON brooks-lint itself: "add a new skill", "edit the brooks-debt guide", "update the eval suite", "fix t
npx skills add hyhmrright/brooks-lint --skill brooks-harness --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# brooks-lint — Maintenance Harness (Orchestrator) This skill orchestrates work **on the brooks-lint repo itself**. It runs a sequential subagent pipeline: each stage is a dedicated agent defined in `.claude/agents/`. Spawn each with the `Agent` tool, `subagent_type` set to the agent name, and **always `model: "opus"`**. Stages depend on each other in order, so this is a pipeline, not a parallel team. ## Pipeline ``` [orchestrator] Phase 0 context check Phase 1 classify request → select stages Phase 2 run selected stages in order, with a QA loop-back: skill-author → eval-curator → consistency-qa ─(FAIL)→ back to author │ PASS ▼ trigger-boundary-auditor (only if a description changed) ▼ release-manager (only if release requested) Phase 3 report + collect feedback ``` ## Phase 0 — Context check Determine the run mode before doing anything: - `_workspace/brooks-harness/` exists + maintainer asks to redo part of a prior run → **partial re-run**: invoke only the affected stage(s), reusing prior notes. - `_workspace/brooks-harness/` exists + a fresh request → **new run**: move the old folder to `_workspace/brooks-harness_prev/`, start clean. - No `_workspace/brooks-harness/` → **initial
- Pipeline
- Phase 0 — Context check
- Phase 1 — Classify the request
- Phase 2 — Run the pipeline
- Phase 3 — Report & feedback
- Conventions this harness enforces
- Error handling
- Test scenarios
What does the brooks-harness skill do?
Maintenance orchestrator for the brooks-lint plugin itself. Runs a sequential subagent pipeline — author → eval → QA → trigger-audit → release — to add or edit a skill, refresh the eval suite, keep the four manifests + all README translations + CHANGELOG + AGENTS/GEMINI in sync, audit trigger boundaries, and cut releases. Drives the five agents in .claude/agents/ (skill-author, eval-curator, consistency-qa, trigger-boundary-auditor, release-manager). Triggers when the maintainer asks to work ON brooks-lint itself: "add a new skill", "edit the brooks-debt guide", "update the eval suite", "fix t
How do I install it?
Run `npx skills add hyhmrright/brooks-lint --skill brooks-harness --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From hyhmrright/brooks-lint, a repository with 1,284 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.