← ClaudeAtlas

codebase-auditlisted

Whole-repo, multi-agent audit that IS the Sprint-end cross-review ceremony (product-wide integrity): 4 axes — spec-conformance, logic/defect hunt, redundancy, and product-security — over the ACCUMULATED codebase at HEAD, not the Sprint diff. Findings are swept to zero per defect class — one class = one PBI covering every occurrence, documentation drift batched into a single DOCS PBI — and non-blocking: EVERY finding is PO-adjudicated, Critical/High carrying a next-Sprint recommendation, and a rejected finding is suppressed with a recorded decision. At Integration-Sprint entry a thin re-check confirms the latest audit is fresh and no open blocking (non-Low) audit PBIs remain before testing proceeds.
sohei56/maul-team · ★ 15 · Code & Development · score 68
Install: claude install-skill sohei56/maul-team
## Role Per-PBI review — the codex reviewers and the 5-aspect Integrity stage — sees one PBI's diff. A diff-scoped gate cannot see defects that only emerge in the **accumulated whole**: dead code that is also an unimplemented requirement, an I/O default that silently disables a feature, a silent failure in the wiring layer, two design specs mandating contradictory behavior, or the same logic implemented twice across PBIs from different Sprints. Those defects survive every diff-scoped gate. This skill closes that gap with a **whole-repo audit at HEAD**, run in two contexts. It is SM-owned and read-only: auditors read and reason, they never edit. | Context | When | Gate semantics | |---|---|---| | **(a) cross-review** (primary) | Every Sprint, embedded in the `cross-review` ceremony | **Non-blocking.** Never fails the Sprint, never transitions the phase. **Every** finding is PO-adjudicated (Step 4a); Critical/High carry a `next_sprint` recommendation, Low a `defer` one. The one exception is the `DOCS` batch, which the ceremony closes inside the current Sprint (`../cross-review/SKILL.md` Step 7b) — documentation drift compounds while it waits. | | **(b) integration entry** (thin re-check) | Once, at the top of `integration-tests` Step 1 | Verifies the latest audit is **fresh** and no open blocking (non-`low`) audit PBI remains. Both hold → proceed. Stale/missing → run a fresh audit; unresolved blocking PBIs → **block** and route to `backlog_created`. | Context (a) is the aud