Fibery
Baz integration guide for Fibery
By pulling in Fibery entity data such as names, descriptions, types, and discussion comments, Baz ensures that every code change is grounded in product context. Reviewers no longer need to switch between Fibery and GitHub to understand why a change exists - they get the full context, right where the code is.
Baz uses Fibery context to:
Enrich AI-generated summaries and topics with your business objectives.
Tailor prompts to reflect the goals and constraints from the Fibery ticket.
Help reviewers focus on what’s important by aligning code changes to the original intent.
Configuring Baz & Fibery
To enable Fibery support:
Go to the Fibery integration section in Settings.
Click Configure and complete the authentication flow.
Once connected to your Fibery workspace, Baz will automatically attach Fibery context to linked pull requests.
Tip: Baz detects linked Fibery entities using entity IDs in branch names or references included in the PR title or description.
How Baz Uses Fibery Data
Once enabled, Baz pulls the following data from linked Fibery entities:
Ticket name and description - used to shape review summaries and reasoning.
Status, priority, and group - helps set reviewer expectations.
Owners and contributors - injected into review prompts to guide validation.
Updates and discussion threads - used to enrich reviewer understanding.
This context is injected into Baz workflows to:
Generate summaries that reflect product intent and scope.
Structure review topics around features, flows, or decisions defined in Fibery.
Guide reviewers to evaluate changes through the lens of what the ticket was designed to accomplish.
Last updated