audit
Branch-aware or full-project review across quality, security, performance, and tests, with focused lenses when you need them.
Invocation
Section titled “Invocation”/audit current the branch delta/audit the full project/audit src/checkout a path/audit current security one lens/audit independent current prepare an independent-review checkpointWhat it writes
Section titled “What it writes”Findings into syntaxis/context/findings.md, and independent-review receipts
into syntaxis/context/review.md.
Severities
Section titled “Severities”| Level | Meaning | Blocks /complete |
|---|---|---|
P0 |
Data loss, security break, cannot ship | Yes |
P1 |
Likely bug, broken contract, missing guard | Yes |
P2 |
Real defect with a workaround | No |
P3 |
Minor or cosmetic | No |
What it guarantees
Section titled “What it guarantees”- The ledger never scopes the review. The code is reviewed fresh, then findings are recorded — a repair can introduce a defect no existing entry points at.
- A finding is never closed implicitly.
- A clean review does not prove the application works. That is
/check’s job.
See Code Quality and The Findings Ledger.