88 review :
99 if : github.event.pull_request.user.login == 'Jordonbc'
1010 runs-on : ubuntu-latest
11+
1112 permissions :
12- id-token : write
13- contents : write
13+ contents : read
1414 pull-requests : write
1515 issues : write
1616
@@ -31,12 +31,44 @@ jobs:
3131 model : ${{ vars.OPENCODE_REVIEW_MODEL }}
3232 use_github_token : true
3333 prompt : |
34- Before anything else, read and follow AGENTS.md for this repository and module.
35- Review this pull request:
36- - Check for code quality issues
37- - Look for potential bugs
38- - Suggest improvements
39- - If you make any code edits, run 'cd Client && just test' to verify they compile and pass tests before committing.
34+ Before doing anything else, read and follow AGENTS.md for this repository and for any affected module.
35+
36+ You are reviewing this pull request only. Do not edit files, do not commit changes, and do not attempt to rewrite the PR.
37+
38+ Review only the changes introduced by this pull request, using surrounding repository context only when needed to understand correctness.
39+
40+ Focus on:
41+ - Correctness bugs
42+ - Regressions
43+ - Unsafe assumptions
44+ - Error handling problems
45+ - API misuse
46+ - Race conditions, lifetime issues, ownership issues, or resource leaks
47+ - Test coverage gaps where the changed behaviour is not adequately covered
48+ - Maintainability issues that would realistically matter in this codebase
49+
50+ Do not comment on:
51+ - Pure style preferences unless AGENTS.md or existing repository conventions clearly require them
52+ - Hypothetical rewrites
53+ - Broad architecture advice unrelated to this PR
54+ - Trivial naming or formatting issues unless they obscure correctness
55+ - Missing tests for code that has no meaningful behavioural change
56+
57+ For every finding:
58+ - Cite the specific file and changed line/range when possible
59+ - Explain why it is a real issue
60+ - Explain the likely impact
61+ - Suggest the smallest reasonable fix
62+ - State confidence as High, Medium, or Low
63+
64+ Use this severity scale:
65+ - Blocking: correctness, data loss, security, build failure, test failure, serious regression
66+ - Important: likely bug, maintainability risk, missing validation, meaningful test gap
67+ - Minor: small cleanup with clear value
68+
69+ Prefer fewer, higher-confidence comments over many speculative comments.
70+
71+ If there are no substantive issues, say that no blocking or important issues were found. Do not invent issues to appear useful.
4072
4173 - name : fallback
4274 if : ${{ steps.review_primary.outcome == 'failure' }}
4981 model : ${{ vars.OPENCODE_REVIEW_MODEL_FALLBACK }}
5082 use_github_token : true
5183 prompt : |
52- Before anything else, read and follow AGENTS.md for this repository and module.
53- Review this pull request:
54- - Check for code quality issues
55- - Look for potential bugs
56- - Suggest improvements
57- - If you make any code edits, run 'cd Client && just test' to verify they compile and pass tests before committing.
84+ Before doing anything else, read and follow AGENTS.md for this repository and for any affected module.
85+
86+ You are reviewing this pull request only. Do not edit files, do not commit changes, and do not attempt to rewrite the PR.
87+
88+ Review only the changes introduced by this pull request, using surrounding repository context only when needed to understand correctness.
89+
90+ Focus on:
91+ - Correctness bugs
92+ - Regressions
93+ - Unsafe assumptions
94+ - Error handling problems
95+ - API misuse
96+ - Race conditions, lifetime issues, ownership issues, or resource leaks
97+ - Test coverage gaps where the changed behaviour is not adequately covered
98+ - Maintainability issues that would realistically matter in this codebase
99+
100+ Do not comment on:
101+ - Pure style preferences unless AGENTS.md or existing repository conventions clearly require them
102+ - Hypothetical rewrites
103+ - Broad architecture advice unrelated to this PR
104+ - Trivial naming or formatting issues unless they obscure correctness
105+ - Missing tests for code that has no meaningful behavioural change
106+
107+ For every finding:
108+ - Cite the specific file and changed line/range when possible
109+ - Explain why it is a real issue
110+ - Explain the likely impact
111+ - Suggest the smallest reasonable fix
112+ - State confidence as High, Medium, or Low
113+
114+ Use this severity scale:
115+ - Blocking: correctness, data loss, security, build failure, test failure, serious regression
116+ - Important: likely bug, maintainability risk, missing validation, meaningful test gap
117+ - Minor: small cleanup with clear value
118+
119+ Prefer fewer, higher-confidence comments over many speculative comments.
120+
121+ If there are no substantive issues, say that no blocking or important issues were found. Do not invent issues to appear useful.
0 commit comments