sjat/boma
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
boma/docs/reviews
History
sjat 1da117d65b docs(review): 2026-06-11 repo audit — fix build-wave doc drift 
/review-repo run at 67f2aba. Auto-fixed 5 safe doc-drift items left by the
base(firewall)+dev_env build wave: README/playbook/role notes that still called
the roles "empty/not built", plus README tree gaps and the reciprocal ADR-021
cross-links in ADR-016/020.

18 open findings reported (not fixed). Headline: `make lint` is red on `main`
(site.yml imports the non-existent docker_host role) and an ADR-004 <-> ADR-022
backup-scope contradiction. Deferral checklist clean (0 stale-deferred); 7 of
12 prior findings confirmed resolved. See docs/reviews/2026-06-11-review.md.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-11 14:48:00 +02:00
..
2026-05-30-findings.json review-repo: harden scanner, apply safe fixes, record first review 2026-05-30 19:10:58 +02:00
2026-05-30-review.md review-repo: harden scanner, apply safe fixes, record first review 2026-05-30 19:10:58 +02:00
2026-06-05-findings.json review-repo: 2026-06-05 report (4 auto-fixed, 12 open) 2026-06-05 18:24:39 +02:00
2026-06-05-review.md review-repo: 2026-06-05 report (4 auto-fixed, 12 open) 2026-06-05 18:24:39 +02:00
2026-06-11-findings.json docs(review): 2026-06-11 repo audit — fix build-wave doc drift 2026-06-11 14:48:00 +02:00
2026-06-11-review.md docs(review): 2026-06-11 repo audit — fix build-wave doc drift 2026-06-11 14:48:00 +02:00
latest.md docs(review): 2026-06-11 repo audit — fix build-wave doc drift 2026-06-11 14:48:00 +02:00
README.md Add /review-repo command with deterministic pre-scan and reviews store 2026-05-30 18:56:01 +02:00

README.md

docs/reviews/

Tracked output of the /review-repo command (one set of files per run). This is an audit trail — committed, not hand-edited. The command writes these files; don't edit them yourself.

Files per run

File Purpose
<YYYY-MM-DD>-review.md Human-readable report
<YYYY-MM-DD>-findings.json Machine-readable findings — used to diff new/recurring/resolved on the next run, and as the cron email payload
latest.md A copy of the most recent report (stable path for quick reference / email)

What a report contains

  • Run metadata — date and the commit SHA reviewed.
  • Summary — finding counts by dimension and severity.
  • Auto-fixes applied — what the run fixed (safe/obvious only), with a file list.
  • Open findings — prioritised, grouped by dimension; each with a location, a suggested fix, and a new / recurring / resolved tag (vs the previous run).
  • Follow-up prompt — a copy-pasteable prompt to act on the open findings.

The four review dimensions and the auto-fix safety rules live in .claude/commands/review-repo.md.