Repository navigation
v0.14.0 — positive feedback, clean-review approval & reviewer interaction
Two feature sets since v0.13.1, both fully opt-in (default-off) via .github/review-bot.yml — with no config changes, behavior is byte-identical to v0.13.1.
Positive feedback & clean-review approval (#37)
positive_feedback:
enabled: true # up to max_items "Highlights" in the review summary,
max_items: 3 # each praising a concrete good decision + why it was good
approval:
celebrate_clean: true # clean review → "✅ Prisma reviewed this PR and found no issues — nice work."
clean_conclusion: success # clean review check conclusion: neutral (default) | successThe reviewer can now celebrate what's good, not just flag what's wrong — including an opt-in real GitHub PR approval on clean reviews.
Reviewer interaction (#38)
interactions:
enabled: true # default false
max_per_review: 3 # hard cap on provider-backed replies per review round (1–25)Developers can discuss the feedback with the reviewer directly on the PR:
@bot ask why is finding 2 a security risk? we sanitize upstream
- Replies are grounded in review context: the latest round's findings and check-run summary.
- When more than one message is allowed, prior exchanges thread into context for later messages.
max_per_reviewhard-caps interactions per review round; a new review round resets the budget. Template replies (disabled / no review yet / cap reached) never call the provider.- The budget ledger is stateless (hidden comment markers — GitHub remains the only durable state) and hardened against forged-marker cap bypass.
- Vendor-neutral: the provider contract gains
respond(), implemented by all adapters (Anthropic, OpenAI, Copilot, deterministic fake for evals).
Verification
1018 tests across 56 files · 23/23 deterministic eval scenarios · vendor-isolation gate green.
Full changelog: v0.13.1...v0.14.0