A review costs 0.1 credit, a tenth of what a dispatched
job costs, and both spend the same credit
balance. There is also a monthly limit on reviews,
counted separately from your monthly limit on jobs.
Request a review
To request a review, add a comment to an open pull request with the command on its own line:Commands are matched against a whole line, ignoring case and extra spacing, so
@Ridgeline-AI review works but please @ridgeline-ai review this does not.
@ridgeline-ai is only the wording of the command — it is not a GitHub
account, so there is nothing to notify and nobody to invite to your
repository.Findings
Ridgeline posts its findings on the pull request itself, as a GitHub review. Each finding is a comment on the line or block of code it concerns, with an explanation and a suggested change where the fix is clear. Findings that don’t map to the diff are listed separately in the review body. Each finding has a severity and a category. Severity can becritical, high, medium, or low, with findings ordered from most to least severe.
Each review includes at most eight findings, prioritizing the most severe.
This keeps the focus on the issues that matter most, rather than overwhelming
the review with every issue found.
@ridgeline-ai review to review any new commits pushed since the last review, and @ridgeline-ai fix to have Ridgeline address the findings.
Fix the findings
To fix findings on a review, add a comment with the command on its own line after an initial review:A fix costs 1 credit, like any dispatched job.
@ridgeline-ai fix command also works outside pull request reviews. When used on a GitHub issue, it starts or re-runs that issue’s job. Similarly, when used in a review you submit on a pull request opened by Ridgeline, it re-runs the job that created the pull request. See Dispatch a Job.

