Agent skill · software engineering · sickn33
brooks-harness
Maintenance orchestrator for the brooks-lint plugin itself.
Why this skill is useful
Adds a complete executable orchestration pipeline for managing the brooks-lint plugin's maintenance, which includes multiple stages and QA processes not covered in public documentation.
What it needs
Requires npm installed locally. About 4k tokens when loaded. Last updated 2026-08-07. 44,571 stars on the source repository.
What this skill does
brooks-lint — Maintenance Harness (Orchestrator) When to Use Use this skill when you need 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 + README + CHANGELOG + AGENTS/GEMINI in sync, audit trigger... 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, subagenttype 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 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-harnessprev/, start clean. No workspace/brooks-harness/ → initial run: create it. Run notes and the QA report live under workspace/brooks-harness/. The real artifacts are the repo files themselves — agents edit skills/, evals/, manifests directly; workspace/ only holds the run's notes and the PASS/FAIL verdict for audit. Phase 1 — Classify the request Pick the minimal set of stages. The QA stage is never skipped — every change is gated. Request author eval QA trigger-audit release --------- :------: :----: :--: :-------------: :-------: Add a new skill ✓ (via new-skill scaffold) ✓ ✓ ✓ — Edit skill / guide content ✓ if codes changed ✓ if description changed — Edit shared/ framework ✓ if risk defs changed ✓ — — Eval suite only — ✓ ✓ — — Fix trigger descriptions ✓ — ✓ ✓ — Release — — ✓ — ✓ Full: change + release ✓ as needed ✓ if applicable ✓ Phase 2 — Run the pipeline Spawn each selected stage as a subagent in order. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills sickn33/brooks-harness--d7b09a