Documentation
How Reviews Run
Every push to a connected repository flows through the same automated pipeline. Here is what happens behind the scenes from push to stored review.
The seven-step pipeline
- 01
Sign In
Create a PolyLever account with email, Google, or GitHub OAuth. Your session JWT unlocks the dashboard and GitHub App setup.
- 02
Install GitHub App
Install the PolyLever GitHub App on your account or organization and select repositories. Each repo syncs as a project.
- 03
Push Code
Push commits to a connected branch. GitHub sends a push webhook with before_sha and after_sha to start the review pipeline.
- 04
Fetch Diff
The worker clones or updates the repo using a short-lived installation token, then runs git diff across the pushed commit range.
- 05
Test Guardrails
100+ automated tests run as a safety check against faulty AI-generated reviews. The full suite is actively being built.
- 06
AI Review
The diff is sent to the configured LLM. The model returns a markdown review covering bugs, security, performance, and maintainability.
- 07
View Results
Open the project review history in the dashboard. Each review shows status, the AI write-up, and the underlying diff side by side.
What triggers a review
Reviews are triggered by a push to any connected repository. Branch creation pushes are skipped. Each review captures the commit range between the previous and new HEAD so PolyLever can diff exactly what changed.
Where results go
Completed reviews are stored per project. Open the Review Dashboard guide to learn how to browse history and read AI output with the full diff.