Credentials. The review uses your provider keys from the shell environment and each run is billed to them.
Who it is forA maintainer who wants a second opinion on a risky PR before approving it.
The problemSetting up CI just to try a reviewer is overkill.
The outcomeA merged multi-model review printed to the terminal, or posted to the PR.
What you need first
- A GitHub repository with Actions
- Provider API keys such as OpenAI and Fireworks
- GitHub CLI for setting secrets
Steps
- Export provider keys in your shell
- Run
npx juror-ai review --pr 1234 --repo owner/name - Read the merged findings
- Post it with
npx juror-ai review --pr 1234 --repo owner/name --post
Prompt for your agent
Run `npx juror-ai review --pr <number> --repo <owner/name>` and summarize the top findings. Confirm duplicate findings from different models were merged into one entry.
Caveat. Cost depends on how many models you configure and the size of the diff.
Use this in your AI agent
Ask your agent
Using the Deduped MCP, get the setup steps for Juror-AI/juror and "Review a single pull request from your terminal"
Add Deduped to Claude Code once
claude mcp add --transport http deduped https://dedupedai.com/mcp
Every Monday: the 5 hottest repos and exactly how to use them. Free, one email a week, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Third-party repos we don't own. AI-written use cases can be wrong. Disclaimer