Free
For individuals and OSS maintainers.
- Up to 3 repos
- Public repos only
- Community support
codingassist reviews each pull request against the acceptance criteria of the work items it implements, then posts a summary, inline findings and a status check on the pull request.
Why teams choose codingassist.bot
AI copilots guess. Static checks are shallow. Humans can't scale. We built a fourth thing.
The PR was approved. The bug still reached production.
I spend half my week writing the same review comments.
And nobody checked it against the ticket.
I now check each pull request against its ticket and post what is done and what is missing.
Checked against the ticket
How a review runs
Nothing changes in how your team works. The review arrives where you already discuss the code.

Pull request

Work items
codingassist
On the pull request
Azure DevOps or GitHub notifies codingassist when a pull request is opened or updated.
The diff, the changed files at the head commit, the linked work items with their acceptance criteria, and related code from the same repository.
Built-in pattern rules run on the diff. A model then reviews the change against each acceptance criterion, and a verification pass drops findings it cannot tie to the code.
One summary comment, inline comments for the findings worth your time, and a status check on the pull request.
On the pull request
#128Verify the new email address before switching accounts
Status checks
codingassist
Summary
Adds a verification step to the email change. The new address is stored as pending and becomes active once its token is confirmed.
Acceptance criteria
The old email stays active until the new one is verified
The verification link expires after 15 minutes
An email already used by another account is rejected
40def request_email_change(user, new_email):41 token = issue_token(user, ttl_minutes=15)42 user.pending_email = new_email43 send_verification(new_email, token)codingassist
HighDuplicate email accepted
The new address is stored without checking whether another account already uses it.
Two accounts can verify the same address, and a password reset then reaches the wrong person.
Fix: Return a conflict when User.exists(email=new_email) before line 42.
Under the hood
Security
Pricing
No per-PR metering. No surprise charges.
Free
For individuals and OSS maintainers.
Team
For teams shipping to production weekly.
Business
For orgs with compliance and scale needs.
Enterprise
Self-hosted, SSO, audit, dedicated support.
FAQ
Most reviewers read the diff on its own. codingassist also reads the work items linked to the pull request and checks the change against their acceptance criteria, so it can tell you a requirement is missing, not only that a line looks wrong.
Connect Azure DevOps or GitHub, choose the repositories, and open a pull request.