Pull Requests
The main review workspace in Baz.
Instead of splitting review work across GitHub tabs, CI , preview deployments, and review tools, Baz brings the entire review flow into a single interface. You can understand the change, inspect implementation details, review comments, validate merge readiness, and approve the PR without leaving the page.
Review Flow
A typical review session in Baz follows a progressive workflow:
Walkthrough
Understand what changed and why
File Tree
Navigate impacted areas
Commits
Review incremental updates
Comments
Resolve findings and discussions
Merge Status
Validate merge readiness
The interface is designed around continuous review rather than one-time approval. Baz tracks review state as the pull request evolves so reviewers can focus only on what changed since the last pass.
AI Walkthroughs
When a pull request opens, Baz generates a structured walkthrough of the implementation.
Instead of starting with raw diffs, the walkthrough explains the change in terms of intent, architecture, and impact. This gives reviewers context before they inspect the actual code.
Each walkthrough is divided into implementation sections. For example:
Multi-line selection in diff view
Adds range selection support inside the diff viewer
Comment context
Updates interaction state and comment creation logic
Selection commenting
Handles active ranges and multi-line discussion behavior
Each section links directly to the relevant implementation area in the diff.
This becomes especially useful in large pull requests where understanding the purpose of a change matters more than scanning modified lines sequentially.
Pull Request Overview
The Overview tab acts as the operational summary of the pull request.
Baz surfaces the current review state directly inside the PR:
Open reviewer comments
Review findings still requiring action
External comments
Comments created outside Baz
Checks passed
CI and validation state
Merge blockers
Missing approvals or unresolved discussions
Instead of manually checking GitHub branch protection rules or CI dashboards, reviewers can immediately see whether the PR is ready to merge.
Navigating the File Tree
The File tree tab organizes all modified files hierarchically.
Each file displays:
Added / removed lines
Understand change size
Review indicators
Identify active discussions
Directory grouping
Navigate large changesets faster
This allows reviewers to quickly identify high-impact areas before diving into implementation details.
Files with high churn or concentrated review activity become immediately visible.
Reviewing Commits
The Commits tab focuses on incremental review.
Baz tracks reviewed and unreviewed commits automatically.
During active review cycles, authors often push multiple follow-up commits after feedback. Instead of rereading the entire pull request, reviewers can focus only on changes introduced since the previous review pass.
This makes iterative reviews significantly faster, especially in long-running pull requests.
Managing Review Comments
The Comments tab centralizes all review discussions.
Every finding includes:
File and line references
Jump directly into implementation
Resolution state
Track open and resolved findings
Fix prompts
Generate implementation guidance
Cursor integration
Send fixes directly into Cursor
Baz is designed to reduce context switching between review and implementation. Reviewers can move directly from a finding to a fix workflow without manually reconstructing the issue.
Merge Status
The Merge status tab aggregates all merge requirements into a single view.
Baz combines:
CI checks
GitHub Actions and validations
Approval requirements
Repository merge rules
Open review threads
Reviewer discussions
Merge blockers
Outstanding requirements
AI Reviewer Reports
Baz reviewers generate structured reviewer reports directly inside the pull request.
Reviewer reports include:
Requirement validation
What the reviewer verified
Evidence references
Supporting implementation details
File and line mappings
Direct references into code
Findings
Problems identified during review
Severity classification
Priority and impact level
Each finding is actionable and connected directly to the relevant implementation area.
Reviewers can resolve findings, rerun reviewers, copy prompts, or apply fixes directly in Cursor without leaving the PR.
Continuous Review
Baz is optimized for iterative development workflows.
Instead of treating review as a static approval step, Baz continuously tracks:
Unreviewed commits
Detect newly introduced changes
Open reviewer findings
Keep review state actionable
Merge readiness
Track release eligibility
CI progression
Monitor validation state
Reviewer activity
Understand review coverage
Last updated