How-to
Included / excluded paths
Keep reviews focused — ignore generated code, lockfiles and vendored files so findings land where they matter.
Most noise on a PR comes from files nobody hand-writes: build output, generated clients, lockfiles, vendored deps. Scope the review with include / exclude in .praxiom.yml.
Scope to what you author
include:
- "src/**"
- "lib/**"
exclude:
- "**/*.min.js"
- "**/*.generated.cs"
- "**/node_modules/**"
- "**/dist/**"
- "**/*.lock"
- "docs/**"excludealways wins overinclude.- Globs are matched from the repo root;
**spans directories.
Cap the blast radius
prIntelligence:
maxFilesPerReview: 20Very large PRs (or generated bulk changes) are also stopped by a hard line-count ceiling before any tokens are spent — see Usage & token quota.
Related
Was this page helpful?