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.
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.
| Step | What you do | Pass condition (objective) |
|---|---|---|
| 1. Anchor | Read the full enclosing symbol or module, not only the diff hunk. | You can state file path and line range (or symbol name + file) you are judging. |
| 2. Evidence | For this finding’s type, run the checks in Verification by Issue Type. | Each required check has an artifact: pasted tool output, file:line citation, or explicit "none" / "N matches" after a repo search—not a claim you "looked." |
| 3. Severity | Assign severity using Severity Calibration. | Label matches the table; requests for net-new code that did not exist in scope are Informational only. |
| 4. Format | Draft the finding for the report. | Matches [FILE:LINE] ISSUE_TITLE; Informational items do not add to the actionable count. |
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
More from existential-birds/beagle
langgraph-code-review
Reviews LangGraph code for bugs, anti-patterns, and improvements. Use when reviewing code that uses StateGraph, nodes, edges, checkpointing, or other LangGraph features. Catches common mistakes in state management, graph structure, and async patterns.
825react-flow
React Flow (@xyflow/react) for workflow visualization with custom nodes and edges. Use when building graph visualizations, creating custom workflow nodes, implementing edge labels, or controlling viewport. Triggers on ReactFlow, @xyflow/react, Handle, NodeProps, EdgeProps, useReactFlow, fitView.
771tailwind-v4
Tailwind CSS v4 with CSS-first configuration and design tokens. Use when setting up Tailwind v4, defining theme variables, using OKLCH colors, or configuring dark mode. Triggers on @theme, @tailwindcss/vite, oklch, CSS variables, --color-, tailwind v4.
595react-flow-advanced
Advanced React Flow patterns for complex use cases. Use when implementing sub-flows, custom connection lines, programmatic layouts, drag-and-drop, undo/redo, or complex state synchronization.
427python-code-review
Reviews Python code for type safety, async patterns, error handling, and common mistakes. Use when reviewing .py files, checking type hints, async/await usage, or exception handling.
426docling
Docling document parser for PDF, DOCX, PPTX, HTML, images, and 15+ formats. Use when parsing documents, extracting text, converting to Markdown/HTML/JSON, chunking for RAG pipelines, or batch processing files. Triggers on DocumentConverter, convert, convert_all, export_to_markdown, HierarchicalChunker, HybridChunker, ConversionResult.
378