PR Reviews
Azent can review pull requests with full codebase context. It reads the changed files, understands the intent behind the changes, and leaves specific, actionable review comments.
How to trigger
Go to a pull request and add a comment:
Or click "Review with Azent" in the PR action menu.
As with work item triggers, the agent replies in the same discussion thread — first by editing a status comment with queue + processing time, then by posting a separate summary comment when the review is complete. The summary points to the individual inline suggestions left on specific lines, so reviewers can jump to them directly.
What the agent does
- Reads the PR description and linked work items to understand intent
- Reads all changed files and their surrounding context
- Analyzes the changes for bugs, security issues, performance problems, and style inconsistencies
- Leaves review comments on specific lines with actionable suggestions
- Posts a summary comment with an overall assessment
Inline suggestions
The inline comments are anchored to the exact lines they refer to, the same way a human reviewer would leave them in Azure DevOps. They show up in the file diff and in the PR's discussion list, so reviewers and the author can resolve them one at a time.
In the example below, Azent left two suggestions on a forgot-password change: one on the TypeScript component (normalize the email before posting, surface the API's 400 message) and one on the template (disable the submit button while invalid / in-flight, add novalidate).
Focused reviews
You can guide the review by adding specifics to your comment: