Documentation
Forseti docs
Forseti reviews every pull request and posts inline findings, a living summary and a check run.
You choose how hard each PR is read, by branch, path and label, and see the price before it runs.
Every finding cites file and line evidence, keeps its ID across pushes and resolves itself when fixed.
Start here
- 1Install the GitHub AppPick the repos. Forseti asks for read access to code and never pushes.Read
- 2Open or pick a pull requestThe first review runs on its own. Every later push gets an incremental review.Read
- 3Set depth where it mattersGlance for docs, Deep for payments. The price is shown before anything is spent.Read
Start
Connect a repo and get the first review.
- Getting startedConnect GitHub, get a first review, and see what Forseti posts on every PR./docs/getting-started
- Install the GitHub AppThe permissions the app asks for, why, and how to change which repos it sees./docs/install-github-app
- Import from other toolsBring rules over from CodeRabbit, Greptile, Bugbot, Copilot, Gemini, Cursor or AGENTS.md./docs/import
Configure
Choose depth, checks and limits, in the dashboard or in a file.
- .forseti.yaml referenceEvery key of the repo config file, with defaults, limits and examples./docs/forseti-yaml
- Policies & depthGlance, Standard and Deep; dimensions, strictness, caps and how the price is worked out./docs/policies-depth
- Domain packsFocused checks for money, migrations, tenancy and auth, PII and architecture./docs/domain-packs
Use
Drive Forseti from the pull request and connect your other tools.
Reference
The API and the questions teams ask most.