> ## Documentation Index
> Fetch the complete documentation index at: https://docs.getblame.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Quickstart

> Begin with a guide on the fastest path to a successful outcome

This guide walks you through connecting your GitHub account, selecting repositories to monitor, and receiving your first automated AI review.

<Card title="**GitHub Cloud & GitHub Enterprise Support**" type="note">
  Blame currently supports all GitHub Cloud and GitHub Enterprise Server installations.
</Card>

<Tip>
  **GitLab & Bitbucket Support:** Native GitLab and Bitbucket integrations are actively in development. If your team requires GitLab early access or self-hosted air-gapped deployments, please reach out to support.
</Tip>

***

## Installation & Setup

```mermaid theme={null}
flowchart LR
    A[1. Install GitHub App] --> B[2. Enable Repositories]
    B --> C[3. Configure Review Standards]
    C --> D[4. Open Test PR]
```

### 1. Install the GitHub App

The Blame GitHub App grants read access to analyze code diffs and write access to post inline review comments.

Log in to your [Blame Dashboard](https://app.getblame.com) and head to **Repositories** (or complete the initial setup wizard). Click **Connect GitHub App** or **Add Repositories**.

In GitHub, select the personal account or organization where you wish to install Blame. Choose your repository permissions:

* **All repositories:** Automatically grants access to current and future repos.
* **Only select repositories:** Manually select specific repositories to review.

Click **Install & Authorize**. GitHub will redirect you back to the Blame workspace with your repositories synced.

***

## Enabling Repositories

Once authorized, your available repositories will appear in your workspace.

Go to [**Repositories**](https://app.getblame.com/repositories). Toggle the switch next to any repository you want Blame to automatically review, or click **Enable All**.

When a repository is enabled for the first time, Blame builds an initial Tree-Sitter AST index to map cross-file dependencies and internal architectural symbols.

<img src="https://mintcdn.com/blame-085dcc89/Ut99rydadS-tKX4L/images/Group-2.png?fit=max&auto=format&n=Ut99rydadS-tKX4L&q=85&s=03bcb17524ddc53e924f05745bcd722f" alt="Group 2" width="2400" height="1260" data-path="images/Group-2.png" />

***

## Review Behavior & Customization

Customize review frequency and strictness under **Repository Settings**.

### Review Triggers

Choose when Blame initiates a review:

* **On PR Opened:** Runs immediately upon PR creation.
* **On New Commits / Synchronize:** Re-evaluates whenever new commits are pushed.
* **Draft PRs:** Toggle whether to evaluate drafts before they are marked ready for review.

### Review Strictness

Fine-tune review feedback density:

* **Low (Comprehensive):** Flags all architectural, security, performance, and style issues.
* **Medium (Balanced):** Prioritizes logic defects, security vulnerabilities, and high-impact warnings.
* **High (Critical Only):** Strict focus solely on P0/P1 defects and breaking API changes.

***

## Create Your First Test PR

Verify your setup with a live pull request.

Create a test branch with a small code change in an enabled repository and open a pull request on GitHub.

Blame analyzes the diff against full repository context and posts a comprehensive review comment with inline diff suggestions.

You can also manually trigger a review at any time by commenting `@blame review` on any GitHub pull request or clicking **Trigger Review** inside the [Blame PR Feed](https://app.getblame.com/pull-requests).

***

## What’s Next?

* Train Blame on your team's code conventions, style guides, and architectural patterns.
* Track review time saved, merge velocity, and defect resolution rates.
* Receive instant summaries and critical bug alerts in your team channels.