# Shortcut

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.

<div data-with-frame="true"><figure><img src="https://3328658395-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FVjqbueGEV6lEh1M5NENO%2Fuploads%2F38krDusZQMI5fIlZBlc0%2FScreenshot%202025-12-18%20at%2015.27.55.png?alt=media&#x26;token=e6838610-6220-4a5b-89e7-90630a10ec77" alt="Configure Shortcut integration"><figcaption><p>Configure Shortcut integration</p></figcaption></figure></div>

#### Configuring Baz & Shortcut <a href="#configuring-baz-and-jira" id="configuring-baz-and-jira"></a>

To enable Shortcut support:

1. Go to the **Shortcut integration** located in Settings > Integrations.
2. Click **Configure** and follow the authentication flow.
3. 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.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.baz.co/basics/integrations/shortcut.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.