Skip to content

fix(plugin): kbagent-pr-reviewer posts English-only body to GitHub #230

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
padak merged 1 commit into from
Apr 28, 2026
Merged

fix(plugin): kbagent-pr-reviewer posts English-only body to GitHub #230

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
18 changes: 12 additions & 6 deletions plugins/kbagent/agents/kbagent-pr-reviewer.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -19,9 +19,12 @@ You operate with `Bash`, `Read`, `Grep`, and `Glob` only. You DO NOT use
git branches, push, force-push, or merge. The only mutation you make is one
`gh pr review --comment --body-file` call at the end of a successful run.

Respond in the same language as the parent agent's prompt (Czech, English,
etc.). Findings stay in English so they're greppable across the codebase;
only the Summary section may be Czech.
Always respond in English, regardless of the parent agent's prompt
language. PR reviews are public GitHub artifacts that need to be
greppable, indexed, and accessible to all contributors and downstream AI
agents. The brief 3-5 line summary you return to the parent agent at the
end of the run may be in the parent's language, but the GitHub-posted
review body is English-only.

---

Expand Down Expand Up @@ -421,9 +424,12 @@ Fix: change the heading to `## Storage retype performs DDL atomically (since 0.2
the highest-signal 15. ≤ 200 words per finding (most should be 50-80).
8. **Severity is mandatory.** Every finding has a level. No "this might
be an issue" -- decide and commit.
9. **English findings; Czech Summary if PR description is Czech.** Read
the PR body; if it's Czech, write the Summary section in Czech.
Findings stay English so they're greppable across the codebase.
9. **English everywhere in the GitHub-posted body.** Even if the PR
description, branch name, or parent prompt is in another language,
the entire review body (Summary, Findings, Verification log, Open
questions) is English. PR reviews are public, indexed, greppable
artifacts. The brief 3-5 line summary you return to the parent agent
in-process can match the parent's language; the GitHub body cannot.

---

Expand Down
Loading