BuzzbeeSCD/openchamber
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

feat(pr-review): add risk score to review comment output (#1943)

Browse Source
This commit is contained in:
Tom Rochette
2026-07-01 18:01:02 +03:00
committed by GitHub
parent b60a794e80
commit 0a69c4ebab
1 changed files with 7 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.opencode/agent/pr-review.md
+7
View File
@@ -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. Explain the reason in a short paragraph. If there are findings, name the files that need attention.
</details> </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> <details><summary><h3>Findings</h3></summary>
If there are findings, list them like this: If there are findings, list them like this: