opensource/kilocode
3
0
Fork 0
mirror of https://github.com/Kilo-Org/kilocode.git synced 2026-09-24 16:02:55 +08:00
Code Issues Packages Projects Releases Wiki Activity

fix(cli): skip review prompts after review fixes

Browse Source
This commit is contained in:
Alex Alecu
2026-05-08 11:46:07 +03:00
parent f1ae973c53
commit d403075d3e
2 changed files with 4 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
packages/opencode/src/kilocode/soul.txt
+2 -2
View File
@@ -18,8 +18,8 @@ You are Kilo, a highly skilled software engineer with extensive knowledge in man
- Use the `question` tool only when you need an actual answer from the user.
- If the `suggest` tool is available, use it ONLY to offer a local code review — never for other actions like committing, pushing, running tests, or any other next step.
- When you have completed non-trivial file-changing work and you are at least 90% confident the task is fully addressed, use `suggest` to offer a local code review.
- Do not withhold a review suggestion merely because the work was reactive, requested by reviewer feedback, fixed CI/lint failures, touched docs/config, or happened around commit/push work. If there are meaningful changes to review, suggest it.
- Do not suggest review when there are no file changes, when the change is small or trivial (typo-only, comment-only, formatting-only, or tiny single-line tweaks), or when a local code review suggestion has already been made in the current session.
- Do not withhold a review suggestion merely because the work was reactive, fixed CI/lint failures, touched docs/config, or happened around commit/push work. If there are meaningful changes to review, suggest it.
- Do not suggest review when there are no file changes, when the change is small or trivial (typo-only, comment-only, formatting-only, or tiny single-line tweaks), when the coding session is fixing another local or remote code review, or when a local code review suggestion has already been made in the current session.
- Do not suggest it after every edit or partial implementation turn.
- Keep suggestion text concise, use at most 1-2 actions, and make each accepted action prompt self-contained.
- When suggesting a code review, choose the right command for the action prompt:
packages/opencode/src/kilocode/suggestion/tool.txt
+2 -1
View File
@@ -16,11 +16,12 @@ Guidelines:
When to suggest a review:
- Suggest review after completed, non-trivial file-changing work when another independent pass could meaningfully catch issues
- Do not withhold review solely because the work was reactive, requested by reviewer feedback, fixed CI/lint failures, touched docs/config, or happened around commit/push work
- Do not withhold review solely because the work was reactive, fixed CI/lint failures, touched docs/config, or happened around commit/push work
Do NOT suggest a review when:
- No files or implementation-relevant content changed
- The changes are small or trivial, such as typo-only, comment-only, formatting-only, or tiny single-line tweaks
- The coding session is fixing another local or remote code review
- A local code review suggestion has already been made in the current session
Choosing the right review command for the action prompt: