Structured Reasoning Template Improves AI Code Review Accuracy

A Reddit user on r/ClaudeAI shared their experience with AI code reviews failing to properly analyze a timezone conversion function. The AI gave a "clean review" but didn't trace where the input came from, producing "review-shaped output" without proper analysis.

The user found a Meta research paper (arXiv:2603.01896) that studied this problem and discovered structured reasoning templates improve code analysis accuracy by 5-12 percentage points. The key insight: change what the model produces, not how you ask it.

The user adapted the research into a complete prompt template they use as a custom command, prepended to every code review request:

You are a code reasoning agent answering questions about a codebase.
You can read files to gather evidence. You CANNOT execute code.

=== RULES ===

Before reading a file, state what you expect to find and why.
After reading a file, note observations with line numbers.
Before answering, you MUST fill in ALL sections below.
Every claim must cite a specific file:line.

=== REQUIRED CERTIFICATE (fill in before answering) ===
FUNCTION TRACE TABLE:



Function
File:Line
Behavior (VERIFIED by reading source)



(List every function you examined.)




DATA FLOW ANALYSIS:
Variable: [name]

• Created at: [file:line]
• Modified at: [file:line(s), or NEVER MODIFIED]
• Used at: [file:line(s)]

SEMANTIC PROPERTIES: Property N: [factual claim about the code]

• Evidence: [file:line]

ALTERNATIVE HYPOTHESIS CHECK: If the OPPOSITE of your answer were true, what would you expect?

• Searched for: [what]
• Found: [what, at file:line]
• Conclusion: REFUTED or SUPPORTED

<answer>[Final answer with file:line citations]</answer>

The template forces the AI to systematically examine functions, trace data flow, verify semantic properties, and check alternative hypotheses before providing a final answer. Each claim must cite specific file and line numbers.