summaryrefslogtreecommitdiffhomepage
diff options
context:
space:
mode:
authorAiden Cline <[email protected]>2025-12-20 11:43:59 -0600
committerAiden Cline <[email protected]>2025-12-20 11:43:59 -0600
commitda6e0e60c0ca42d54595553fc1ab70f62be6e3b9 (patch)
treece9ae5e55f785b786b49baeb900c2d0d0aee2ec3
parentd89b567b47ae2709f0fe3fd1e997860073829d72 (diff)
downloadopencode-da6e0e60c0ca42d54595553fc1ab70f62be6e3b9.tar.gz
opencode-da6e0e60c0ca42d54595553fc1ab70f62be6e3b9.zip
ci: adjust review agent prompt to discourage bad diffs
-rw-r--r--.github/workflows/review.yml2
1 files changed, 2 insertions, 0 deletions
diff --git a/.github/workflows/review.yml b/.github/workflows/review.yml
index 36f6df54f..c0e3a5deb 100644
--- a/.github/workflows/review.yml
+++ b/.github/workflows/review.yml
@@ -67,6 +67,8 @@ jobs:
When critiquing code style don't be a zealot, we don't like "let" statements but sometimes they are the simpliest option, if someone does a bunch of nesting with let, they should consider using iife (see packages/opencode/src/util.iife.ts)
Use the gh cli to create comments on the files for the violations. Try to leave the comment on the exact line number. If you have a suggested fix include it in a suggestion code block.
+ If you are writing suggested fixes, BE SURE THAT the change you are recommending is actually valid typescript, often I have seen missing closing "}" or other syntax errors.
+ Generally, write a comment instead of writing suggested change if you can help it.
Command MUST be like this.
\`\`\`