Shortcut
Baz's Shortcut Integration
By pulling in story information like titles, descriptions, story types, acceptance criteria, and stakeholder comments, Baz ensures that every change request is grounded in intent. Reviewers no longer need to switch between Shortcut and GitHub to understand why a change exists - they get the full context, right where the code is.
Baz uses this context to:
- Enrich AI-generated summaries and topics with your business objectives.
- Tailor prompts to reflect the goals and constraints from the Shortcut ticket.
- Help reviewers focus on what’s important by aligning code changes to the original intent.
Configuring Baz & Shortcut
To enable Shortcut support:
- Go to the Shortcut integration located in Settings > Integrations.
- Click Configure and follow the authentication flow.
- Once connected to your Shortcut Workspace, Baz will automatically attach ticket context to linked change requests.
Tip:
Baz detects relevant Shortcut stories when the branch name includes a Shortcut story token (e.g.sc-1234), or PR description references a Shortcut story link.
How Baz Uses Shortcut Story Data
When connected, Baz pulls:
- Story title and description - used to shape review summaries and reasoning.
- Story type (feature, chore, bug) - helps set reviewer expectations.
- Acceptance criteria - injected into review prompts to guide validation.
- Comments and discussion threads - used to enrich reviewer understanding.
This context flows through all downstream Baz workflows:
- Summaries reflect the purpose of the story.
- Break down topics based on feature or flow relevance.
- Guide reviewers to evaluate changes through the lens of what the ticket was designed to accomplish.
FAQ
How does Baz know which Shortcut item a change relates to?
From a Shortcut story token in the branch name, for example sc-1234, or a Shortcut story link in the pull request description.
What does Baz read from Shortcut?
Story title and description, story type, acceptance criteria, and comments and discussion threads.
Does connecting it change what reviewers see in the code host?
Yes, in the sense that the review itself gets richer: summaries, topics, and agent prompts carry the intent from Shortcut, so reviewers do not have to open the tracker to understand why a change exists.
Nothing is attached to my pull request, what should I check?
Check that the integration is connected under Settings, Integrations, that the branch name or pull request description carries a recognizable identifier, and that the connected account can see the item in Shortcut.