build-review-loop

Build-Review Loop

Orchestrate N rounds of build → review → fix → re-review using different models for building vs reviewing (cross-model diversity). The orchestrator (Hermes) manages the loop, verifies independently, and delivers structured reviews.

MANDATORY: delegate the build — never hand-code mid-loop

User correction: "didnt see you using cursor cli". The orchestrator started hand-writing fixes in the repo instead of dispatching Cursor. That violates this skill's core contract even when the fix is small. Non-trivial dev work means: orchestrator writes a spec file, Cursor (user's default: cursor-grok-4.6-high, --force) implements, orchestrator verifies independently, Codex/Claude/Cursor review, iterate. Hand-editing is only acceptable for trivial mechanical fixes (a typo, a one-line version bump) — and even then, say so explicitly when deviating. If unsure whether it counts as non-trivial, delegate.

See also references/generated-frontmatter-and-reviewer-outages.md — reviewer-lane outage substitution pattern + the f-string YAML frontmatter double-failure class (:/# scalars break YAML; safe_dump default width wraps it) + the untracked-files reviewer trap. See also references/persistent-loop-plan.md — multi-session or multi-batch loops: loop state lives in loop-*.md files, not memory; resume with scripts/loop_plan_check.py, attest briefs with scripts/attest_file.py. Ported from planning-with-files; the native plugin was NOT installed (see references/planning-with-files-adaptation.md). See also references/evidence-pairs.md — every delivered batch carries a before/after evidence pair (screenshot, measured number, or output pair), embedded in the PR body or delivery message. Ported from michaelshimeles/skills. See also references/mobile-app-verification.md — APK/dex/baked-config artifact verification gates, version stamping, the 4-layer Android WebView network stack (cleartext / mixed-content / ws scheme / CORS), backgrounded-JavaScript login-death bugs, multi-round review convergence on lifecycle code. See also references/sync-pipeline-review-patterns.md — reviewing app ↔ external-source-of-truth sync code (Google Sheets, SaaS mirrors): fetch-inside-lock, status-clear scoping to processed snapshots, append reconcile/marker placement under dynamic column maps, blank-cell semantics, static-path auth whitelists. See also references/review-findings-adjudication.md — adjudicating reviewer BLOCKINGs against the dispatch spec (dismiss with cause, never silently), the four recurring test-quality findings (hook-bypass, loose string-greps, single-open DOM tests, over-broad state selectors) and their fixes, and fix-round routing back to the builder. See also references/production-reachability-review.md — the dead-feature cluster: public functions with tests but zero production callers (unreachable user stories while the suite stays green), test-only enrichment kwargs the runtime never passes, and the per-batch grep pass that catches it. See also references/extraction-from-filled-docs.md — fill-template extraction domain depth: fingerprint/structural context, collapse ordering + XML validity + unclaimed-content preservation, path-escape and hardlink guards, and the reviewer traps for extraction code.