From 0a69c4ebabff4517c4a365dae766eac595d22125 Mon Sep 17 00:00:00 2001
From: Tom Rochette <roctom@gmail.com>
Date: Wed, 1 Jul 2026 11:01:02 -0400
Subject: [PATCH] feat(pr-review): add risk score to review comment output
 (#1943)

---
 .opencode/agent/pr-review.md | 7 +++++++
 1 file changed, 7 insertions(+)

diff --git a/.opencode/agent/pr-review.md b/.opencode/agent/pr-review.md
index 07913c13..c7c1c924 100644
--- a/.opencode/agent/pr-review.md
+++ b/.opencode/agent/pr-review.md
@@ -136,6 +136,13 @@ Merge signal in plain English: safe to merge, safe after a small fix, or not saf
 Explain the reason in a short paragraph. If there are findings, name the files that need attention.
 </details>
 
+<details open><summary><h3>Risk Score: X/5</h3></summary>
+
+1 is low risk (isolated, reversible, well-contained change), 5 is high risk (touches security, data persistence, shared state, build/release, or broad cross-runtime contracts).
+
+Explain the score in a short paragraph: which risk dimensions apply (correctness, data loss, security/supply-chain, performance, cross-runtime parity) and what makes the change more or less risky.
+</details>
+
 <details><summary><h3>Findings</h3></summary>
 
 If there are findings, list them like this: