First review in 10 minutes
A hands-on tour from an Azure DevOps pull request to a verified review, end-to-end.
This tutorial takes you from a fresh codingassist.bot workspace to your first verified pull request on Azure DevOps in about ten minutes. By the end you will have:
- Onboarded your Azure DevOps organization and connected a repository
- Linked a work item with acceptance criteria to a PR
- Triggered a review and read the reasoning trace it emits
Prerequisites
| Requirement | Why |
|---|---|
| An Azure DevOps organization | The Git provider supported today |
| Organization administrator | Onboarding the org requires membership of Project Collection Administrators — see Roles |
| A repository with an open (or draft) PR | This is what gets reviewed |
| A work item with Acceptance Criteria, linked to the PR | The review anchors against the ACs — see AC verification |
The flow
Create your workspace
Sign in at app.codingassist.bot with your Azure DevOps / Microsoft account. The organization administrator who onboards the org becomes its Owner. The Free tier is enough to follow along.
Connect your Azure DevOps project
From Settings → Integrations → Azure DevOps, click Connect. codingassist.bot registers a service-hook subscription for Pull request created / updated on the project. Full detail: Connect Azure DevOps.
Link a work item with acceptance criteria
On the ADO PR, make sure a work item is linked and that its Acceptance Criteria field is filled. codingassist.bot resolves the linked items automatically — see Work items & ticket sources.
Open or update the pull request
Create the PR (or push a new commit). Within seconds, codingassist.bot posts a thread comment with the verdict and updates the PR status check (
codingassist).
Read the reasoning trace
The verdict comment links to a reasoning trace — the deterministic record of how codingassist.bot bound each acceptance criterion to a verifiable piece of the diff.
32def update_email(user, new):33 validate(new)34 if user.pending_email:35 return "verify first"3651def issue_token(user):52 token = make_token(ttl=900)5367def 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 + linked work items + repo graph), ran independent reasoning planes, then orchestrated a verdict with confidence scoring.
For the whole picture, read The 3-stage pipeline — it explains every box in the flow you just triggered.
Where to next?
- Connect Azure DevOps — the connection, in detail
- Work items & ticket sources — how ACs are resolved
- Tune what gets reviewed — the
.praxiom.ymlreference - Acceptance-Criteria verification — the check others can't do