Reads the ticket. Walks the repository. Traces what the diff can break. Then leaves a review worth reading — with fixes you can commit in one click.
Changed files
Where it runs
GitHub App
One install, per-repository access, no token to rotate. Reviews start on their own — or from a CI/CD step, or an @scout comment.
Pull request reviews
Inline comments anchored to the line, each with a suggestion you can commit from the PR.
Checks & merge gates
The merge-safety score is published as a status check, so you can require it on protected branches.
Jira issues
The linked ticket is pulled in and the diff is checked against its acceptance criteria.
Language-aware review — idioms, standard library and ecosystem conventions per stack.
Capabilities
Capabilities
It writes the review, not a summary of the diff
Reviewer attention
A retried webhook will refund twice. Stripe dedupes on idempotencyKey — every other mutation in this file already passes one.
Try it — the fix lands on the PR branch as its own commit.
How it works
You configure the first stage and the last. The middle three are the reason the review is worth reading.
A webhook fires the moment a pull request opens, updates or is re-requested — nothing to wire up. When you’d rather ask for it, run Scout as a step in your CI/CD pipeline or comment @scout on the pull request. Draft PRs stay quiet until you mark them ready.
Scout resolves the linked Jira issue, clones the repo at the merge base, reads your configuration, and builds a call graph of everything the diff touches.
Language-aware analysis runs alongside SAST, secret and dependency scanners. Findings are cross-checked against the ticket's acceptance criteria and your team's standards.
Candidate findings are deduplicated, scored, and dropped unless they change what a reviewer would do. What survives carries a confidence value and the rule that produced it.
A summary, an architecture diagram, inline comments with committable fixes, and a merge-safety score — posted as a single review the author can act on top to bottom.
0
Capabilities shipped
not a roadmap
0+
Languages reviewed
idiom-aware
0
Scanners on every diff
SAST · secrets · SCA
0
Step to install
a GitHub App · CI optional
Highlights
The linked Jira issue is pulled in and the change is checked against its acceptance criteria — the difference between “it compiles” and “it does what was asked”.
A call graph is walked out of every changed symbol, so the review covers the untouched code your diff puts at risk.
Every finding carries a concrete replacement, applied as its own commit on the PR branch.
Merge safety, backed by coverage, ticket criteria and blast radius — published as a status check.
SAST, secrets and dependencies — reported only where this pull request introduced them.
Accepts, edits and dismissals reweight rules per repository, so the review sounds more like your team every week.
Learned
Dismissed twice in this repo — the rule stops firing here, and Scout records why.
Twelve more ship alongside them — PR summaries, architecture diagrams, conversational chat on the PR, review configuration with explicit precedence, and hand-off to a coding agent.
Install the GitHub App, pick your repositories, open a pull request. The review shows up on its own.