Getting Started
Ensure your team makes the most of Baz.
Getting Started with Baz: A Three-Week Ramp-Up
This guide outlines the recommended path for teams to get the most out of Baz during their first three weeks. It distills insights from internal discussions and typical customer onboarding patterns.
Overview
Baz reviews your codebase with purpose‑built agents, dedicated contexts and essential tools. To adopt Baz effectively, teams should start with the default configuration, affirm agent suggestions, and gradually introduce advanced capabilities.
The following plan breaks down how teams typically reach full value within 21 days.
Week 1 — Baseline Setup
Goal: Enable core Baz capabilities and validate expected behavior.
Install Baz via GitHub App (or GitLab token) and ensure read & write access is approved.
Start with Baz Agents - managed agents, designed to be consistent, predictable, and aligned with common code review best practices.
Confirm that code reviews are being triggered and that agent output is consistent using Insights.
Exclude non‑critical paths (e.g., autogenerated files, test snapshots) to reduce noise.
Add key integrations such as Jira/Linear Ticketing System (if applicable) to enable Spec Reviewer.
Week 2 — Tune Your Agents
Goal: Adjust Baz to match your workflows and development conventions.
Review Recommended Agents settings and enable optional agents as needed.
Filter review types by agent (e.g., usage, checks, breaking changes).
Encourage users to respond back to reviewers to add Memories that further customize and personalize agent recommendations.
Where persistent reviews are not required, consider transitioning repositories to "on‑demand" review/summary/graph using Configurations.
Week 3 — Optimize for Scale
Goal: Use Baz to improve review quality, reduce cycle time, and support larger teams.
Encourage developers to develop and test Custom Agents to enforce standards that are not covered by Baz or Recommended agents. Use the Playground to test and optimize agent prompts.
For all reviewers, re-evaluate acceptance rates and memory functions are functioning well.
Evaluate where additional automation or path exclusions may be required.
Summary
By following this progression, teams quickly reach a stable and efficient review workflow. Week 1 focuses on establishing a consistent baseline; Week 2 tailors Baz to your team; Week 3 unlocks deeper automation and broader impact.
Last updated