Review

Solo Issue Discovery Rounds

Use these rounds only through the solo issue-campaign skill.

1. Freeze one exact commit and record the dependency lock, provisioning command, and supported environment contract before starting. Derive that environment contract from package engines, public documentation, repository CI, peer requirements, published package behavior, and explicit user decisions; do not narrow it ad hoc, and treat an unresolved conflict as a blocker on CLEAN.
2. Inventory all tracked files, package and public API families, implementation owners, generated artifacts, test harnesses, workflows, documentation contracts, supported platforms, and open and closed issue or pull-request history before examining candidates. Reconcile that inventory with git ls-files and with the campaign's mandatory coverage matrix. A grep lens, a sampled file set, or a statement that the surface was reviewed is not coverage.
3. Audit the entire inventory and execute the whole mandatory matrix. Audit source, tests, documentation, CI, packaging, generated artifacts, platform behavior, upstream and downstream provenance, and history against the development skill's Forbidden section. Continue through the full inventory after finding a candidate.
4. Treat the matrix as a floor. Cover all applicable public operation families and direct, factory, and nested forms; equivalent TypeScript spellings, including aliases, interfaces, call and construct type literals, and classes; local, re-exported, module, package, user-global, default-library, ambient, and runtime-native provenance; union, intersection, generic, and transform-option interactions; static, dynamic, array, any, and unknown value contexts; positive, one-axis negative, boundary, malformed, maximum-width, one-past-boundary, and mutation controls; generated-byte and executed-runtime behavior; deterministic repeat emit; workspace, clean packed, and deployment consumers; and supported Node, module-resolution, operating-system, and CLI paths. Every interaction that reaches shared control flow is its own cell, and every positive cell has a one-axis negative twin. Run mutations only in a disposable checkout, keep the regression probe unchanged, and require the probe's canonical command to fail. When the round discovers a new owner, consumer, axis, or interaction, version and re-hash the canonical matrix and execute the added cells before the round can complete.
5. Record every raw candidate, killed hypothesis, command, and artifact in the campaign knowledge base with the exact commit, environment, matrix hash, and census results. The round is COMPLETE only when the full inventory and current matrix finished; otherwise it is INCOMPLETE and cannot support a CLEAN campaign state.
6. Reopen each candidate from primary evidence in a fresh state, reproduce it, verify ownership and provenance, trace its complete consequence surface, and compare existing issues and pull requests. Record accept, partial acceptance, rewrite, combine, split, reject, or defer with the supporting evidence, so a later round does not rediscover a rejected premise as new. Implementation mechanisms remain hypotheses.
7. If any meaningful candidate survives, return to step 3 and run another complete round against the same frozen commit before publishing or implementing anything, and repeat until one round produces no surviving candidate. Discovery owns this loop; it never hands a partial candidate pool to publication or implementation because the first round already found work. A prior finding never permits narrowing the next round to its owner or neighbors.
8. Publish only the surviving adjudicated form when the campaign is authorized to publish. After the authorized issue and implementation flow completes, freeze the new integrated commit and begin the next full-scope round.
9. Stop only when one immutable-state round completes the entire repository inventory and mandatory matrix, no round is INCOMPLETE, and no meaningful candidate survives verification. Any verified in-repository correctness, contract, data-integrity, build, test-oracle, documentation, packaging, workflow, or Forbidden violation is meaningful regardless of severity, rarity, legacy status, or malformed-input trigger. Do not downgrade a proved defect to an observation to satisfy the stop rule. An unresolved, deferred, or unimplemented verified defect blocks CLEAN, and green existing suites cannot satisfy the stop rule.

Explicit Multi-Agent Reviews

When the user explicitly asks for a team, parallel, or multi-agent review, load the multi-agent skill and its review procedure instead of this workflow. It inherits the same whole-surface, immutable-state, and auditable-completeness law while defining independent parallel reviewers, agent briefing, and lead and critic adjudication.