ti.sil/pr-agent
1
0
Fork 0
mirror of https://github.com/qodo-ai/pr-agent.git synced 2025-12-12 02:45:18 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

docs: refactor super exhaustive mode as maximum coverage configuration recipe

Browse source
This commit is contained in:
ofir-frd 2025-09-21 12:19:11 +03:00
parent 063d0999c5
commit ccfc24ea85
1 changed files with 30 additions and 32 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

62
docs/docs/tools/improve.md
View file

@ -488,38 +488,6 @@ Available options:
We recommend starting with `regular` mode, then exploring `exhaustive` mode, which can provide more comprehensive suggestions and enhanced bug detection.
### Super exhaustive mode
> `💎 feature`
For maximum suggestion comprehensiveness and thorough code analysis, you can enable the super exhaustive mode. This configuration combines the exhaustive suggestions depth with significantly increased suggestion limits to provide the most thorough code review possible.
```toml
[pr_code_suggestions]
suggestions_depth = "exhaustive"
enable_suggestion_type_reuse = true
num_code_suggestions_per_chunk = 100
num_best_practice_suggestions = 100
```
This mode is recommended for:
- Critical code reviews requiring maximum coverage
- Final reviews before major releases
- Code quality audits
???- warning "Performance considerations"
Super exhaustive mode will significantly increase:
- Analysis time and API costs
- Number of suggestions generated (potentially overwhelming)
- Comment volume in your PR
Use this mode judiciously and consider your team's review capacity.
### Self-review
> `💎 feature. Platforms supported: GitHub, GitLab`
@ -587,6 +555,36 @@ This approach has two main benefits:
Note: Chunking is primarily relevant for large PRs. For most PRs (up to 600 lines of code), Qodo Merge will be able to process the entire code in a single call.
#### Maximum coverage configuration
> `💎 feature
For critical code reviews requiring maximum coverage, you can combine several settings to achieve a "super exhaustive" analysis. This is not a built-in mode, but a configuration recipe for advanced use cases.
```toml
# Recipe for maximum suggestion comprehensiveness
[pr_code_suggestions]
suggestions_depth = "exhaustive"
enable_suggestion_type_reuse = true
num_code_suggestions_per_chunk = 100
num_best_practice_suggestions = 100
```
This configuration is recommended for:
- Critical code reviews requiring maximum coverage
- Final reviews before major releases
- Code quality audits
???- warning "Performance considerations"
This configuration will significantly increase:
- Analysis time and API costs
- Number of suggestions generated (potentially overwhelming)
- Comment volume in your PR
Use this configuration judiciously and consider your team's review capacity.
## Configuration options
???+ example "General options"