Split evidence-grounding row and move summary table to top
Splits the summary table's combined 'Candidate finding validation /
evidence discipline' row into two independent rows matching the
existing §3 (candidate finding validation) and §6 (evidence grounding)
detailed sections, renumbering the table to 12 rows. The new Evidence
grounding row is populated strictly from §6's existing evidence (code
evidence attribution, typed authoritative/informational provenance,
CodeRabbit's 'receipts' claim) - no new research.
Also relocates the Review-engine summary table (and its interpretation
note) to immediately after the opening research-snapshot paragraph, so
a reader reaches the comparison before the longer scope/framing,
label-definition, and pipeline sections. Table content is otherwise
unchanged; no other section was modified.
Add review-engine summary table to AI-Code-Review-Landscape
Adds an 11-dimension executive-summary table right after the pipeline
diagram and before the detailed dimension-by-dimension sections, so a
reader can scan the main methodological differences in ~20-30s. Reuses
the citations/evidence already established in the detailed sections
below (no new research); every cell links back to its numbered section.
Uses a consistent vocabulary (explicit contract / documented / vendor
claim or benchmark / not publicly specified) instead of checkmarks,
since the evidence differs in kind, and adds an interpretation note
clarifying that 'not publicly specified' is a documentation gap, not a
capability claim.
Reframe AI-Code-Review-Landscape around review-engine methodology
Rewrite the comparison to ask how engines reason about a change
(review-target correctness, context reasoning, candidate-finding
validation, root-cause consolidation, finding placement, evidence
grounding, severity semantics, decision derivation, re-review state,
uncertainty discipline, behavioral evaluation) instead of comparing
product feature breadth. Excludes IDE UX, pricing, SaaS integrations,
autofix-as-a-feature, and similar product-capability axes as explicitly
out of scope for an engine-quality comparison.
Incorporates the merged review-base-policy invariant (issue #134) and
the current candidate-finding-validation, root-cause-consolidation,
finding-placement, contextual-evidence, and finding-confidence models.
Re-verifies competitor claims against current public documentation for
Cursor Bugbot, GitHub Copilot code review, CodeRabbit, Qodo Merge, and
Greptile, marking undocumented dimensions 'Not publicly specified'
rather than inferring internals.
Add a common Wiki Page Map to every page for navigation
Appends an identical, compact "Wiki Page Map" table (Page / What it
covers) to the end of all 22 existing Wiki pages, so a reader landing
on any single page can see every other page and its purpose without
returning to Home first.
No _Sidebar.md or _Footer.md exists in this wiki, so there is no
native shared-rendering mechanism that would place identical content
inside every page's own body; the table is duplicated intentionally
(kept small, one heading, one table) rather than introducing a
partial or page-specific navigation aid.
No substantive content, technical claims, or existing links were
changed — this is a pure addition at the end of each page.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Sync Wiki with the implemented Adaptive Specialist Depth architecture (#268)
Adds a Specialist-Depth Review page documenting the final Tier 3
architecture (base reasoning -> materially implicated concern ->
evidence-driven specialist-depth decision -> 0..N deepening
capabilities -> one unified review) and the five capabilities that
actually landed (Security, Distributed Systems, Database/Migration,
Performance, Dependency/Supply-Chain), grounded in
shared/policies/specialist-depth.md and review-scope.md. Wires it into
Home, How the Review Model Works, Architecture Overview, the
Repository Documentation Map, Review Context and Existing Evidence
(explicit-focus additive-only), the Local Code Review guide
(capability provenance field), the AI Code Review Landscape
positioning section, and the FAQ.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
docs: establish code review project wiki
Add the initial GitHub Wiki: 14 explanatory/navigational pages covering
onboarding, Skill selection, the review model, architecture, per-Skill
guides, review context/evidence, severity/decision model, packaging, a
dated AI code-review landscape analysis, the development workflow, an
FAQ, and a repository documentation ownership map. All content links
out to canonical repository files rather than duplicating policy text.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>