Docs

Troubleshooting

Quick checks to get every pull request reviewed, and how to adjust agents, budgets and skills.

Get a pull request reviewed

Start with the pull request itself: whenever PURA holds a review back, for a budget, a plan limit or agent scoping, it leaves a comment that names the reason. Then check:

  1. Is the pull request ready for review? PURA reviews once a draft is marked ready.
  2. Has a review started? PURA reviews automatically when a pull request is opened, marked ready or gets new commits. To start one on demand, comment /pura review.
  3. Is PURA turned on for this pull request? If a repo admin commented a bare /pura ignore, comment /pura review to turn PURA back on.
  4. Is PURA installed on the repository? In GitHub, open your installed apps and click Configure next to PURA to add it.
  5. Is your account on a trial or paid plan? Choose a plan in the dashboard to keep reviews running after the trial.
  6. Is there review allowance left this month? Check usage in the dashboard. The allowance resets on the 1st, or you can upgrade for more.
  7. Does the repository fit your plan's download size? Each plan reviews repositories up to a set size (Starter: 25MB, Scale: 50MB, Pro: 100MB). Upgrade for larger repositories.

A budget was reached

PURA pauses reviews when a budget is reached, so spend stays within your numbers. To keep reviewing:

  • Raise the budget on the agent, or on the team, author, repository or pull request rule that covers this pull request.
  • Add another provider to the agent as a fallback.
  • Wait for the reset: daily at midnight UTC, weekly on Monday, monthly on the 1st.

The analytics dashboard shows your current spend against each budget.

Make an agent apply to the pull request

An agent reviews a pull request when all of these hold:

  • Its status is Active.
  • Its first provider has an API key. The trial agents run on PURA's trial model and need none.
  • Its scoping rules allow the pull request's team, author, repository or labels.
  • Its .pura-routing instructions include this kind of change. A rule like “do not run for docs-only changes” leaves docs pull requests to your other agents.

Quickest fix: keep one Active agent with a key, no scoping rules and no routing. It reviews every pull request.

A review posted an error comment

PURA retries short provider outages on its own. If a review still posts an error comment, check the API key on the agent in the dashboard, then comment /pura review to run it again.

Get an agent to use its skill

  • Merge the skill to the default branch. PURA reads skills from there.
  • Name the folder exactly like the agent's name, for example .agents/skills/security-agent/SKILL.md.
  • For a custom skill, give its SKILL.md frontmatter a name and a description, and use a model that supports tool calling.
  • If Sanitize holds back a custom skill you fully trust, turn Sanitize off for that skill.

Choose which model reviews

Each provider on an agent has a default, high and low model, and the agent's routing instructions pick one per pull request. To change the result:

  • Refine the routing: edit .pura-routing in the agent's skill so the right changes pick the right tier.
  • Change the models in the default, high and low slots on the agent.
---
name: security-agent
description: Security-focused code review.
.pura-routing: |
  Use this only for nodejs files. For large changes, use the high model.
---

See Routing for more examples.

Contact support

Email support@pura.sh and we'll help you sort it out.

Next

Getting started

Install PURA and request your first review

Configuration

Review agents, providers, models and scoping