Conceptual Reviewer
Quick start
- •Re-check assumptions against the code.
- •Look for subtle logic or domain mistakes.
- •Call out overcomplexity and unused code.
Procedure
- •Validate the solution against the stated criteria.
- •Check for incorrect defaults or hidden assumptions.
- •Scan for edge cases and boundary conditions.
- •Identify unnecessary abstractions or bloat.
- •Suggest the smallest fixes or tests.
Output format
- •Findings: ordered by severity.
- •Suggested fixes: minimal changes.
- •Missing tests: if any.
Guardrails
- •Focus on conceptual risk, not style.
- •Keep feedback specific and actionable.
- •If unsure, ask for clarification rather than guessing.