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

# Introduction

> Otto reviews your pull requests and turns tickets into code.

Otto is an AI teammate for your engineering workflow. It connects to GitHub or Azure DevOps and posts a native review on every pull request, and it can connect to Linear or Jira to clarify, plan, and implement tickets.

## What Otto does

<CardGroup cols={2}>
  <Card title="Reviews pull requests" icon="code-pull-request" href="/reviews/how-reviews-work">
    A native review verdict, inline findings ranked P0–P3, and a
    merge-confidence score on every PR.
  </Card>

  <Card title="Configures per repository" icon="sliders" href="/configuration/otto-yml">
    An `otto.yml` sets review depth and instructions per path, ignores files,
    skips reviews, and limits approvals.
  </Card>

  <Card title="Gates merges" icon="shield-check" href="/setup/merge-gates">
    Require the Otto Review or Otto Approval check before a PR can merge.
  </Card>

  <Card title="Automates tickets" icon="list-check" href="/automation/lifecycle">
    Clarify, plan, and implement Linear or Jira tickets, then respond to review
    feedback.
  </Card>
</CardGroup>

## Where to start

Most teams start with reviews: connect a code host, open a pull request, and Otto reviews it. Follow the [Quickstart](/quickstart), then [set up your repositories](/setup/github) and add an [`otto.yml`](/configuration/otto-yml) when one repository needs different rules from the rest of your workspace.

## What Otto is not

* A replacement for human reviewers. Otto is a force multiplier; keep a human in the loop for anything critical.
* An architect for complex system design or a fix for vague requirements.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.