Credentials. Provider keys are stored as GitHub secrets; the workflow skips fork PRs so the keys are not exposed to outside code.
Who it is forA team lead who wants AI code review without paying for a hosted review seat per developer.
The problemA single AI reviewer is one opinion and can be confidently wrong.
The outcomeA posted PR review with merged findings, a merge score and a cost receipt.
What you need first
- A GitHub repository with Actions
- Provider API keys such as OpenAI and Fireworks
- GitHub CLI for setting secrets
Steps
- Export your key with
export JUROR_OPENAI_API_KEY=… - Run
npx juror-ai init --set-secretsin the repository - Or preview changes first with
npx juror-ai init --dry-run - Open a pull request and read the posted review
Prompt for your agent
Set up Juror-AI/juror in <repo> with `npx juror-ai init --dry-run`, then `npx juror-ai init --set-secrets`. Open a test PR and confirm the review includes a merge score and a cost receipt.
Caveat. The sample workflow only reviews PRs from the same repository, so fork contributions are not reviewed automatically.
Use this in your AI agent
Ask your agent
Using the Deduped MCP, get the setup steps for Juror-AI/juror and "Add multi-model AI review to every pull request"
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