core practice · system design prompt
Design exercise: Code Review Systems
Diff understanding, intent, correctness, maintainability, risk ranking, review workflows, and actionable findings. Implement designOutline() returning non-empty values for: changeIntent, riskFinding, actionableEvidence. Each value must name a concrete mechanism or decision.
The mechanism
Useful review connects a changed line to behavior and risk. Findings need evidence, severity, scope, and a concrete remediation—not generic style commentary.
Expected evidence
A design outline with changeIntent, riskFinding, actionableEvidence plus an explicit failure mode or trade-off.
Try this drill in the practice workspace →
Hints when you need them
- Name the failure mode before selecting the mechanism.