Review Verification Protocol

Review Verification Protocol

This protocol MUST be followed before reporting any code review finding. Skipping these steps leads to false positives that waste developer time and erode trust in reviews.

Anti-confabulation (gate 0 — applies to ALL review/verify skills)

Before issuing any verdict — confirm, reject, sever, fix, or adjudicate — you MUST echo the exact artifact you are judging, quoted from a source you read in this turn:

• For a code finding: the file:line plus the cited code, read freshly now (not recalled from earlier in the session).
• For a diff review: the actual diff hunk under review.
• For a structured report (e.g. verify-llm-artifacts adjudicating findings[]): the finding's id + file + line + description, printed from the parsed source file, not from memory.

The artifact is the only source of truth. Never infer what you are reviewing from the branch name, the working directory, surrounding files, or recollection. If your mental model differs from the freshly read source, the source wins. A verdict issued without a same-turn echo of its target is invalid — emit the echo first, or do not emit the verdict.

This gate exists because an LLM under contextual priming will confidently adjudicate things that are not in the file. It runs before the per-finding hard gates below. Skills that consume this protocol implement it concretely: verify-llm-artifacts (Load + ECHO + ID-lock gate), review-llm-artifacts (echo finding before writing JSON), llm-artifacts-detection (anchor FILE:LINE from an opened buffer).

Hard gates (sequence)

Apply once per finding before it may appear in the review. If a gate fails, omit the finding, downgrade to Informational (per Severity Calibration), or rephrase as a question—do not ship soft accusations.

Style-only or preference items must fail gate 2 or map to Do NOT Flag At All—they do not get a severity.

Pre-Report Verification Checklist

Before flagging ANY issue, verify (these items are what gate 2 must produce evidence for):

• I read the actual code - Not just the diff context, but the full function/class
• I searched for usages - Before claiming "unused", searched all references
• I checked surrounding code - The issue may be handled elsewhere (guards, earlier checks)
• I verified syntax against current docs - Framework syntax evolves (Tailwind v4, TS 5.x, React 19)
• I distinguished "wrong" from "different style" - Both approaches may be valid
• I considered intentional design - Checked comments, project conventions (e.g. AGENTS.md or CLAUDE.md), architectural context

Verification by Issue Type

"Unused Variable/Function"

Before flagging, you MUST:

1. Search for ALL references in the codebase (grep/find)
2. Check if it's exported and used by external consumers
3. Check if it's used via reflection, decorators, or dynamic dispatch
4. Verify it's not a callback passed to a framework

Common false positives:

• State setters in React (may trigger re-renders even if value appears unused)
• Variables used in templates/JSX
• Exports used by consuming packages

"Missing Validation/Error Handling"

Before flagging, you MUST:

1. Check if validation exists at a higher level (caller, middleware, route handler)
2. Check if the framework provides validation (Pydantic, Zod, TypeScript)
3. Verify the "missing" check isn't present in a different form

Common false positives:

• Framework already validates (FastAPI + Pydantic, React Hook Form)
• Parent component validates before passing props
• Error boundary catches at higher level

"Type Assertion/Unsafe Cast"

Before flagging, you MUST:

1. Confirm it's actually an assertion, not an annotation
2. Check if the type is narrowed by runtime checks before the point
3. Verify if framework guarantees the type (loader data, form data)

Valid patterns often flagged incorrectly:

typescriptCopy code
// Type annotation, NOT assertion
const data: UserData = await loader()

// Type narrowing makes this safe
if (isUser(data)) {
  data.name  // TypeScript knows this is User
}

"Potential Memory Leak/Race Condition"

Before flagging, you MUST:

1. Verify cleanup function is actually missing (not just in a different location)
2. Check if AbortController signal is checked after awaits
3. Confirm the component can actually unmount during the async operation

Common false positives:

• Cleanup exists in useEffect return
• Signal is checked (code reviewer missed it)
• Operation completes before unmount is possible

"Performance Issue"

Before flagging, you MUST:

1. Confirm the code runs frequently enough to matter (render vs click handler)
2. Verify the optimization would have measurable impact
3. Check if the framework already optimizes this (React compiler, memoization)

Do NOT flag:

• Functions created in click handlers (runs once per click)
• Array methods on small arrays (< 100 items)
• Object creation in event handlers

Severity Calibration

Critical (Block Merge)

ONLY use for:

• Security vulnerabilities (injection, auth bypass, data exposure)
• Data corruption bugs
• Crash-causing bugs in happy path
• Breaking changes to public APIs

Major (Should Fix)

Use for:

• Logic bugs that affect functionality
• Missing error handling that causes poor UX
• Performance issues with measurable impact
• Accessibility violations

Minor (Consider Fixing)

Use for:

• Code clarity improvements
• Documentation gaps
• Inconsistent style (within reason)
• Non-critical test coverage gaps

Informational (No Action Required)

Use for:

• Improvements that require adding new dependencies or modules
• Suggestions for net-new code that didn't exist in the codebase before (new modules, test suites, abstractions)
• Architectural ideas for future consideration
• Test infrastructure suggestions (new mock libraries, behaviour extraction)
• Optimizations without measurable impact in the current context

These are NOT review blockers. They should be noted for the author's awareness but must not appear in the actionable issue count. The Verdict should ignore informational items entirely.

Do NOT Flag At All

• Style preferences where both approaches are valid
• Optimizations with no measurable benefit
• Test code not meeting production standards (intentionally simpler)
• Library/framework internal code (shadcn components, generated code)
• Hypothetical issues that require unlikely conditions

Valid Patterns (Do NOT Flag)

TypeScript

React

Testing

General

Context-Sensitive Rules

React Keys

Flag array index as key ONLY IF ALL of these are true:

• Items CAN be reordered (sortable list, drag-drop)
• Items CAN be inserted/removed from middle
• Items HAVE stable identifiers available (id, uuid)
• The list is NOT completely replaced atomically

useEffect Dependencies

Flag missing dependency ONLY IF:

• The value actually changes during component lifetime
• Stale closure would cause incorrect behavior
• The value is NOT a ref (refs are stable)
• The value is NOT a stable callback (useCallback with empty deps)

Error Handling

Flag missing try/catch ONLY IF:

• No error boundary catches this at a higher level
• The framework doesn't handle errors (loader errorElement)
• The error would cause a crash, not just a failed operation
• User needs specific feedback for this error type

Before Submitting Review

Final verification: 0. Each finding passed Anti-confabulation (gate 0) — its target was echoed from a source read in this turn, not recalled or inferred.

1. Each finding passed Hard gates (sequence) (anchor, evidence with artifacts, severity, format).
2. Re-read each finding and ask: "Did I verify this is actually an issue?"
3. For each finding, can you point to the specific line that proves the issue exists?
4. Would a domain expert agree this is a problem, or is it a style preference?
5. Does fixing this provide real value, or is it busywork?
6. Format every finding as: [FILE:LINE] ISSUE_TITLE
7. For each finding, ask: "Does this fix existing code, or does it request entirely new code that didn't exist before?" If the latter, downgrade to Informational.
8. If this is a re-review: ONLY verify previous fixes. Do not introduce new findings.

If uncertain about any finding, either:

• Remove it from the review
• Mark it as a question rather than an issue
• Verify by reading more code context