First review in 10 minutes

This tutorial takes you from a fresh codingassist.bot tenant to your first verified pull request in about ten minutes. By the end, you will have:

• Connected a Git provider and a ticket source
• Triggered your first review on a real PR
• Inspected the reasoning trace codingassist.bot emits

Prerequisites

The flow

The end-to-end pipeline you'll exercise looks like this:

1. Install the GitHub App

   From the codingassist.bot dashboard click Connect Git → GitHub. You'll be redirected to GitHub to authorise the install. Pick a single repo to start; you can broaden later.

2. Link a ticket source

   codingassist.bot needs to read acceptance criteria. Connect Jira, Linear or GitHub Issues. Take note of the project key.

3. Push a branch with a reference to a ticket

   Push any branch whose head commit message references a ticket id (e.g. [PRX-42] add email verification).

4. Open the pull request

   Within seconds, codingassist.bot posts a comment with the verdict and a deep link to the reasoning trace.

Trigger a review from the CLI

If you'd rather not wait for the webhook, the CLI gives you the same review on demand:

curl -X POST https://api.codingassist.bot/v1/reviews \
  -H "Authorization: Bearer $CODINGASSIST_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "repo": "acme/web",
    "pr": 42,
    "ticket": "PRX-42"
  }'

Read the reasoning trace

The verdict comment contains a link to a reasoning trace — the deterministic record of how codingassist.bot bound each acceptance criterion to a verifiable code contract.

32def update_email(user, new):
33  validate(new)
34  if user.pending_email:
35    return "verify first"
36 
51def issue_token(user):
52  token = make_token(ttl=900)
53 
67def reject_dup(new):
68  if email_exists(new):
69    raise Duplicate()

Each AC maps to one or more lines of the diff. Hover an AC to see the bound contract; codingassist.bot signs and stores this mapping for replay.

What just happened?

Behind the scenes, codingassist.bot ran the 3-stage pipeline: it built context (diff + ticket + repo graph), ran six independent reasoning planes, then orchestrated the verdict with confidence scoring.

If you want the whole picture, jump to The 3-stage pipeline — that page explains every box on the diagram you just generated.

Where to next?

• Connect Azure DevOps — same flow, different provider
• Use BYOM — OpenAI — bring your own model key
• POST /v1/reviews — the full request/response reference