Skip to content

feat(pr-review): score confidence on 1 to 10 so clean reviews read safe - #1276

Merged
Makisuo merged 2 commits into
mainfrom
feat/pr-review-confidence-ten
Oct 6, 2026
Merged

Makisuo merged 2 commits into
mainfrom
feat/pr-review-confidence-ten

Merge origin/main into feat/pr-review-confidence-ten

cf2d749
Select commit
Loading
Failed to load commit list.
Maple Review Bot / Maple / review succeeded Oct 6, 2026 in 3m 44s

Confidence 4/5 · No issues found

🟢 Confidence 4/5 · likely safe to merge
Self-contained rescale with matching tests; the migration's 1 AND 5 guard is the one spot that depends on the deploy ordering.
quality 100/100 · no findings · tests covered · risk medium

Rescales PR review confidence from 1–5 to 1–10 with whole-point deductions, matching caps, a recalibrated prompt and a migration that doubles stored values. Contained and tested; safe to merge in the same deploy as the migration.

  • confidencePrReview scores 1–10: whole-point deductions, caps at 2/4/6/8
  • Check conclusion is success from 7 through prReviewConfidenceTone, was 4
  • Comment, check title and web UI now render /10
  • New migration doubles stored report_json.confidence from 1–5 to 2–10

Fixed since the last review

  • ✅ F1 · Migration doubles confidence with no upper bound
What was checked
  • Migration only rewrites 1 AND 5 values and doubles the Held at N reason with them (.../20261006231211_pr_review_confidence_ten/migration.sql:5-18)
  • Every old cap and label maps to exactly twice the new one (5/4/3/2/1 → 10/8/6/4/2), so the doubling matches the rescale
  • No 1–5 assumption survives outside the updated call sites (grep for /5, Confidence [0-9], confidence threshold comparisons)

cf2d749 · Updated on every push. Reply "won't fix" to dismiss a finding, or mention @maple-review-bot to ask about one.