code-review

Intent

• Perform analysis only unless the user explicitly asks for edits.
• Prioritize actionable, evidence-based findings over general advice.
• Optimize for high-signal findings, not exhaustive commentary.
• Default to review behavior that matches the active agent instructions unless the user asks for a different report shape.

Communication Style

• Use plain language. Avoid jargon when a simpler phrase works.
• Do not offer alternate report versions unless the user explicitly asks.
• Avoid hedging, consultancy tone, and explanatory filler.
• Do not pad findings with soft language such as "makes it hard to reason about", "the only real decision is", or similar framing.

Scope Expectations