Inline review with a verdict
Comments land on the lines they are about, each with a severity and a suggested fix. The review approves or requests changes, like a teammate would.
PRNeuron reviews every pull request with Claude. It checks the change against its Jira ticket, scans for leaked secrets and vulnerable dependencies, and draws what changed — before anyone on your team reads a line.
50 reviews a month free. No credit card. Installs as a GitHub App.
Adds a per-IP limit to the login route. One blocking issue: the limit trusts a header any client can set.
PRNeuron is a GitHub App. There is nothing to add to your CI and nothing to run on your machines.
Pick the repositories PRNeuron may see. Connect Jira if you want reviews checked against tickets.
Every opened, reopened or updated pull request is queued for review automatically.
Inline comments on the exact lines, a summary, and a verdict: approve or request changes.
Most AI reviewers only see the diff. PRNeuron also reads what the work was for, what your team's rules say, and what the change does to the system.
Comments land on the lines they are about, each with a severity and a suggested fix. The review approves or requests changes, like a teammate would.
PRNeuron finds the ticket key in the branch, title or description and checks the change against its acceptance criteria — so "done" means done.
Leaked secrets and known-vulnerable dependencies are caught on every pull request, with a deeper security pass when a change touches auth, queries or input handling. Findings above your threshold block the merge.
Each review opens with a diagram of the affected flow as it was and as it will be, with new, changed and removed steps marked. Reviewers see the shape of the change first.
A graph of every merged pull request, the history of any single file, and a plain-language explanation of what each commit and PR changed — and whether it matched its ticket.
Reads the standards you already keep in the repo — CLAUDE.md, AGENTS.md, Cursor rules, .codereview/rules.md — and applies each one only to the files it covers.
Built for teams who need to know where their code goes before they install anything.
| GitHub permission | Access |
|---|---|
| Contents | Read |
| Pull requests | Read & write |
| Metadata | Read |
Write access is used for one thing: posting the review on the pull request. PRNeuron never pushes code or changes settings.
Any language in a GitHub repository. Reviews work from the diff and the surrounding code, so there is no per-language setup. Dependency vulnerability checks cover npm, Yarn, pnpm, Python (pip, Poetry, uv, Pipenv), Go and Rust lock files.
Claude, by Anthropic. Your organisation can choose the model used for reviews in its settings.
No. It is a first reviewer: it catches the mechanical issues, the security slips and the missed acceptance criteria, so your team's review time goes on design and intent.
Not yet — GitHub only, including private repositories and organisations.
One completed review of one push to a pull request. Opening a PR and then pushing two more commits is three reviews. Commit and PR explanations in the history view do not count towards your allowance.
Yes. It is on by default, and organisation settings let you switch it off or choose the severity — critical, high or medium — at which a finding blocks the merge.
Install the GitHub App, open a pull request, and see your first review in a couple of minutes.
Start free — 50 reviews a month