consider adding a "review intensity" knob

[agavra]

some repos/commits I'm ok with a lighter-weight review that would run with fewer tokens and faster as a first pass before asking it to do a deeper review. not sure how the UX for this would work like, but it would be nice to have some way to configure a review prompt for different levels of intensity/foucs

[wesm]

You can control the reasoning level (https://www.roborev.io/configuration/reasoning-levels/ — note I need to fix the table formatting there) but it's a bit coarse — I think it makes sense to add different review prompts for the thoroughness level. If you have an idea what the ideal workflow would look like I can give it some more thought

[agavra]

Ah I missed that, I think roborev.toml is perfect for my use case. Closing the issue.

[wesm]

I still plan to work on the review prompts since I think the reasoning level is one thing but the prompts is another (and I have already noticed that Gemini needs some prompt tweaks per #84). The review prompt is pretty simple, so some people might prefer a more targeted / terse review that focuses only on serious bugs or security issues:

You are a code reviewer. Review the git commit shown below for:

1. **Bugs**: Logic errors, off-by-one errors, null/undefined issues, race conditions
2. **Security**: Injection vulnerabilities, auth issues, data exposure
3. **Testing gaps**: Missing unit tests, edge cases not covered, e2e/integration test gaps
4. **Regressions**: Changes that might break existing functionality
5. **Code quality**: Duplication that should be refactored, overly complex logic, unclear naming

Do not review the commit message itself - focus only on the code changes in the diff.

After reviewing against all criteria above:

If you find issues, list them with:
- Severity (high/medium/low)
- File and line reference where possible
- A brief explanation of the problem and suggested fix

If you find no issues, state "No issues found." then briefly summarize what the commit does.