[GH-ISSUE #161] bonk: improve review prompt #36

Closed
opened 2026-05-06 12:36:42 +02:00 by BreizhHardware · 4 comments

Originally created by @elithrar on GitHub (Feb 27, 2026).
Original GitHub issue: https://github.com/cloudflare/vinext/issues/161

Originally assigned to: @elithrar on GitHub.

When invoked in a comment, Bonk can occasionally reply to the wrong issue or PR number. This is a problem and needs to be fixed.

Example: https://github.com/cloudflare/vinext/pull/45

We should review the viguy prompt and ensure that the agent is better steered towards ONLY commenting on the issue or PR it was invoked on.

When updating the prompt, ensure you follow anthropic best practice practices for prompt engineering and LLM guardrails.

research

Look at previous workflow runs where Bonk ran, and use that to cross reference issues and PRs. Look at the last 3-4 days of Bonk responses.

You should also reference a related issue at https://github.com/cloudflare/workerd/pull/6150 - however this applies to new pull request automation and not manual comment-driven automation.

Originally created by @elithrar on GitHub (Feb 27, 2026). Original GitHub issue: https://github.com/cloudflare/vinext/issues/161 Originally assigned to: @elithrar on GitHub. When invoked in a comment, Bonk can occasionally reply to the wrong issue or PR number. This is a problem and needs to be fixed. Example: https://github.com/cloudflare/vinext/pull/45 We should review the viguy prompt and ensure that the agent is better steered towards ONLY commenting on the issue or PR it was invoked on. When updating the prompt, ensure you follow anthropic best practice practices for prompt engineering and LLM guardrails. ## research Look at previous workflow runs where Bonk ran, and use that to cross reference issues and PRs. Look at the last 3-4 days of Bonk responses. You should also reference a related issue at https://github.com/cloudflare/workerd/pull/6150 - however this applies to new pull request automation and not manual comment-driven automation.
Author
Owner

@elithrar commented on GitHub (Feb 27, 2026):

/bigbonk research this problem and then propose a fix

<!-- gh-comment-id:3972912021 --> @elithrar commented on GitHub (Feb 27, 2026): /bigbonk research this problem and then propose a fix
Author
Owner

@ask-bonk[bot] commented on GitHub (Feb 27, 2026):

@elithrar Bonk workflow failed. Check the logs for details.

View workflow run · To retry, trigger Bonk again.

<!-- gh-comment-id:3973047010 --> @ask-bonk[bot] commented on GitHub (Feb 27, 2026): @elithrar Bonk workflow failed. Check the logs for details. [View workflow run](https://github.com/cloudflare/vinext/actions/runs/22488831314) · To retry, trigger Bonk again.
Author
Owner

@elithrar commented on GitHub (Feb 27, 2026):

/bonk research this problem and then propose a fix.

<!-- gh-comment-id:3973061676 --> @elithrar commented on GitHub (Feb 27, 2026): /bonk research this problem and then propose a fix.
Author
Owner

@ask-bonk[bot] commented on GitHub (Feb 27, 2026):

APIError: Bad Request: {"success":false,"result":[],"messages":[],"error":[{"code":2005,"message":"Failed to get response from provider"}]}

github run

<!-- gh-comment-id:3973083033 --> @ask-bonk[bot] commented on GitHub (Feb 27, 2026): APIError: Bad Request: {"success":false,"result":[],"messages":[],"error":[{"code":2005,"message":"Failed to get response from provider"}]} [github run](/cloudflare/vinext/actions/runs/22488831314)
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/vinext#36
No description provided.