Reviewers
Turn on review bots for pull requests and tune their settings.
A reviewer extension runs inside each review fix round in prs mode, one per review bot. greptile, coderabbit and macroscope ship today. Turn one on with ./install.sh --with greptile, or list it on the WITH line of skills.conf, as Turn Them On shows.
Each extension reads its bot's result on the PR and says one of four things: the PR is done, it needs fixes, it needs a re-review within the budget, or it goes back to you. Each reviewer's role decides whether that answer can hold the PR. reviewers.md states the full rules, and any extension that ships a reviewer.conf follows them.
Which Bots Run
Nothing to set up per repo. Whether a repo runs a bot is read from that bot's own check on the PR, so a repo running any of them, or none, works as it is.
A bot that can't review the head commit (rate limited, skipped, or paused with no budget left) steps aside when another reviewer reviewed it. When none did, the PR goes back to you.
Roles
Every reviewer is required unless a repo or machine says advisory. A required reviewer holds the PR the way every reviewer always has: the agent waits for its review, fixes what it finds, asks it to review again within its budget, and hands the PR back when it says so.
An advisory reviewer's findings are still triaged and fixed while its budget lasts. Its waiting, its re-review asks, its rate limits and its spent budget never hold a layer, findings it still has open once that budget is spent included, so once the required reviewers are done the PR moves on, and the agent posts no re-review trigger for the advisory one. Its own line still shows what it said.
A PR whose required reviewers are all absent or unavailable treats its advisory reviewers as required, exactly as if no role were set. A required reviewer that is still waiting stays required: the PR waits on it, and advisory answers still can't hold it.
For example, one repo keeps Greptile required and makes CodeRabbit advisory:
git config --local skills.coderabbit.role advisoryIn that repo skills settings coderabbit prints role=advisory and skills settings greptile prints role=required, so a rate limited CodeRabbit no longer holds a PR Greptile has reviewed. A second repo holds the reverse:
git config --local skills.greptile.role advisoryThere skills settings greptile prints role=advisory and skills settings coderabbit prints role=required, so Greptile's spent budget no longer holds a PR CodeRabbit is done with. Only you set a role. The agent never writes a skills. key, and Reviewer Roles lists where the setting can live.
What the Agent Writes on a PR
Only these, and replies only in threads where review bots are the only authors:
- A reviewer's bare trigger, such as
@greptileaior@coderabbitai review. - A reply to a finding that is wrong, or whose fix needs explaining.
- A resolved thread, once a push fixes the finding or the reply is posted.
A thread you or anyone else has joined gets a drafted reply for you instead, and the agent leaves it open.
Settings
Each reviewer declares its settings in its own reviewer.conf. Override one in ~/.agents/skills.conf, or for a single repo in its local git config, which wins.
| skills.conf key | git config key | default | allowed |
|---|---|---|---|
CODERABBIT_REREVIEWS | skills.coderabbit.rereviews | 3 | 0 to 9 |
CODERABBIT_THRESHOLD | skills.coderabbit.threshold | major | critical, major, minor, trivial |
CODERABBIT_CRITICAL_THRESHOLD | skills.coderabbit.critical-threshold | minor | critical, major, minor, trivial |
CODERABBIT_ROLE | skills.coderabbit.role | required | required, advisory |
GREPTILE_REREVIEWS | skills.greptile.rereviews | 2 | 0 to 9 |
GREPTILE_THRESHOLD | skills.greptile.threshold | 4 | 1 to 5 |
GREPTILE_CRITICAL_THRESHOLD | skills.greptile.critical-threshold | 5 | 1 to 5 |
GREPTILE_AUTO | skills.greptile.auto | yes | yes, no |
GREPTILE_ROLE | skills.greptile.role | required | required, advisory |
MACROSCOPE_REREVIEWS | skills.macroscope.rereviews | 2 | 0 to 9 |
MACROSCOPE_THRESHOLD | skills.macroscope.threshold | medium | critical, high, medium, low |
MACROSCOPE_CRITICAL_THRESHOLD | skills.macroscope.critical-threshold | low | critical, high, medium, low |
MACROSCOPE_ROLE | skills.macroscope.role | required | required, advisory |
Local git config is never committed, so a PR can't change what an agent spends.
A threshold set in Greptile's dashboard wins over threshold. A plan marked critical raises the
bar to at least critical-threshold.
For CodeRabbit and Macroscope, rereviews caps the reviews the agent asks for. Their automatic
reviews still count against that budget. Greptile's auto says whether it reviews every PR on
its own. Set it to no where it does not, and the agent asks for a Greptile review only on a PR
it judges worth one, such as risky or large changes, and says why in its handback. After that it
asks again only when the score calls for it. That first review does not count against
rereviews.
The approvability check adds no findings to fix. While it is pending on a clean PR, the round
waits for it, up to the pending cap. A clean PR that Macroscope did not approve comes back as
done clean not-approved, and on a critical plan it goes back to you.
A value outside the allowed set is skipped with a note, and the value below it stays: the
skills.conf value under a bad repo value, the default under a bad skills.conf value. A line
in skills.conf that no installed reviewer claims is skipped with a note too.