What Coderbuds adds
Each pull request gets one Coderbuds comment, edited in place as things change, so there is never a pile of bot comments to scroll past. If your team has a review policy, it also gets a Review policy check beside CI on GitHub.
The comment, line by line
Every line leads with the verdict in bold, then the evidence for it. A line only appears once there is something to say.
| Line | What it says |
|---|---|
| ๐ฏ Quality | A score out of 100 from Coderbuds' own analysis of the diff, with its label. Below Excellent, it says what held the score back. Dependency updates are not scored, and a change too large to read says so instead. |
| ๐ฆ Size | How big the change is against your team's limit, not counting tests, docs and generated files. See Coderbuds Standards. |
| ๐ค Authorship | Which coding agent wrote it, and whether a person read it. An agent's own report decides this; otherwise it is inferred and says so. See Usage Tracking. |
| ๐ Review | How much review your policy asks for (โ none, ๐ an AI review, ๐ a person, ๐ two people) and the reason that decided it. Once that review is in on the latest commit, it reads Reviewed or AI review passed. See Review Policy. |
| ๐ Deployed | Added once the change reaches production, with how long after merge. See Deployment Setup. |
Quality score
The score combines measured facts about the change โ its size, how many files it touches, how focused it is โ with an AI read of the code itself. The same scale is used on the pull request and on your dashboard.
| Score | Label |
|---|---|
| 90โ100 | Elite |
| 80โ89 | Excellent |
| 70โ79 | Good |
| 60โ69 | Average |
| 50โ59 | Below Average |
| 40โ49 | Needs Improvement |
| Below 40 | Poor |
The score is not the review
The quality score describes a change. It never counts as a review โ Coderbuds does not grade its own homework.
When Coderbuds says a change needs an AI review, it means a reviewer you add: the Claude workflow Coderbuds provides, Claude Code Review, or an AI reviewer such as Copilot. Comments on particular lines come from that reviewer. With the Claude workflow, Coderbuds posts them as one review headed AI review ยท Claude. Set one up.
The Review policy check
On GitHub, with a review policy on, a Review policy check sits beside CI. It turns green once the review the policy asks for is in on the latest commit. Its detail lists every reason the change needs that review, which files to read first, and rates the change for Impact, Verification, Rollback cost, Error detection and Alignment.
Until then it only reports. To make it stop merges, see Making it the gate.
Turning the comment off
The comment is on for every repository you add. To stop it for one, open the repository from Team settings → Repositories and switch off AI Comments. Coderbuds keeps scoring the repository's pull requests for your dashboard either way.