reviewer_mode

Structured code review outputs follow a consistent format that includes risk assessment, guardrails, and traceable rationale. This enforces a strict reviewer persona, avoiding ambiguity and ensuring policy-compliant reviews with concrete improvement suggestions.

Risk assessment during a code review applies a strict reviewer persona to produce a structured critique highlighting issues, improvements, and rationale. It enforces a robust code-of-conduct with explicit guardrails to ensure traceable, policy-compliant recommendations.

The best way to review technical documentation for quality assurance is to adopt an Expert Technical Reviewer persona that delivers precise, critical technical reviews. It produces a structured critique highlighting issues, improvements, and rationale in a single pass.

A strict reviewer persona enforces quality standards in static analysis by rejecting vague approvals and demanding a robust code-of-conduct. It generates structured review outputs with risk assessment, guardrails, and traceable rationale for every recommendation.

You can review both code and documentation in a single pass by inspecting the target material and producing a concise, structured critique. This applies an Expert Technical Reviewer persona to deliver precise critical feedback with risk assessment and concrete improvement suggestions.