What You’ll Learn
- How auto-generated code reviews work
- Types of analysis performed
- Interpreting review results
Code Review Analysis
Code Review analyzes changes across multiple dimensions:| Category | Focus |
|---|---|
| Security | Vulnerability scanning, injection risks, credential exposure |
| Accessibility | Accessibility compliance and best practices |
| Performance | Algorithmic complexity, resource usage, scalability |
| Call-chain Impact | Downstream effects on dependent code |
| Type | Description |
|---|---|
| Must Fix | Critical issues that should be addressed |
| Suggestions | Recommended improvements |
Auto-Generate Settings
Configure automatic generation in Settings → Chat:| Setting | Behavior |
|---|---|
| Auto Generate Code Review | Generates quality review after changes |
Review Results
Code review results appear in the Review Changes component. Result Structure:| Section | Content |
|---|---|
| Summary | Overall assessment of changes |
| Issues Found | Specific problems identified |
| Suggestions | Recommended improvements |
| File Breakdown | Per-file analysis |
Best Practices
| Practice | Why |
|---|---|
| Enable auto-review | Catch issues immediately |
| Address critical issues first | Security and stability priority |
FAQs
Does code review slow down the workflow?
Does code review slow down the workflow?
Slightly. Reviews add processing time after task completion. For quick iterations, you can disable auto-review in Settings → Chat.
Do reviews use credits?
Do reviews use credits?
Yes. Code reviews consume credits based on the model used and the amount of code analyzed.
Can I disagree with review findings?
Can I disagree with review findings?
Yes. Review findings are suggestions, not requirements. Use your judgment about what to address.
What languages are supported?
What languages are supported?
Code Review supports all major programming languages. Analysis quality may vary by language.