[PR #168] [MERGED] improve viguy agent triage, community PR evaluation, and known patterns #365

New issue

Closed

opened 2026-05-06 12:39:26 +02:00 by BreizhHardware · 0 comments

BreizhHardware commented

2026-05-06 12:39:26 +02:00

Owner

📋 Pull Request Information

Original PR: https://github.com/cloudflare/vinext/pull/168
Author: @elithrar
Created: 2/27/2026
Status: ✅ Merged
Merged: 2/27/2026
Merged by: @elithrar

Base: main ← Head: fix/viguy-triage-and-patterns

📝 Commits (1)

a223291 improve viguy agent triage, community PR evaluation, and known patterns

📊 Changes

1 file changed (+65 additions, -1 deletions)

View changed files

📝 .opencode/agents/viguy.md (+65 -1)

📄 Description

Follows up on #163. The scope constraint fixed the cross-issue commenting problem, but the viguy prompt still had no guidance for triage vs. implementation, evaluating community PRs, or recognizing recurring issue patterns.

Reviewed the last 4-5 days of issues (#25, #50, #71, #72, #100, #109, #143, #144, #145) and PRs (#127, #131, #136, #140, #141, #142, #147, #151, #153, #154) to identify patterns. Several community PRs were closed as non-problems, duplicates, or misdiagnoses (e.g., #136 added JSX pragmas for a scenario that doesn't occur; #131/#153/#154 were duplicates; #147 duplicated #123). The agent had no framework for catching these before investing review effort.

add "Triage vs. implementation" section after the scope constraint — gives the agent explicit permission to assess-then-decide rather than always jumping to code. defaults to triage when the triggering comment is ambiguous.
add "Evaluating community PRs" section with concrete quality signals: missing issue link, duplicate detection, root cause mismatch, vacuous tests (tests that pass without the fix), unrelated drive-by changes, and LLM-generated description boilerplate. includes tone guidance for community-facing comments.
add "Known issue patterns" table encoding the 6 most commonly reported root causes (RSC/SSR environment boundary, jsx-runtime CJS/ESM interop, missing shim exports, routing regex, package manager detection, immutable headers). saves re-investigation time when the same root cause gets reported again.
add duplicate PR check as step 3 in "Before starting work" — the agent now explicitly checks for existing open/closed PRs addressing the same issue before starting implementation.
add "Response structure" section near the end (recency placement) enforcing assessment-first output: assessment, evidence, then exactly one recommendation (implement/close/needs-info/defer). prevents jumping to implementation on a misdiagnosed problem.

Prompt structure follows Anthropic best practices: highest-priority behavioral constraints at the top (primacy), output formatting near the end (recency), concrete examples over vague directives, and explicit negative constraints ("do not fix by adding JSX pragmas to individual files").

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/cloudflare/vinext/pull/168 **Author:** [@elithrar](https://github.com/elithrar) **Created:** 2/27/2026 **Status:** ✅ Merged **Merged:** 2/27/2026 **Merged by:** [@elithrar](https://github.com/elithrar) **Base:** `main` ← **Head:** `fix/viguy-triage-and-patterns` --- ### 📝 Commits (1) - [`a223291`](https://github.com/cloudflare/vinext/commit/a223291b6d951d9e3b1dfae13495023d89082b6b) improve viguy agent triage, community PR evaluation, and known patterns ### 📊 Changes **1 file changed** (+65 additions, -1 deletions) <details> <summary>View changed files</summary> 📝 `.opencode/agents/viguy.md` (+65 -1) </details> ### 📄 Description Follows up on #163. The scope constraint fixed the cross-issue commenting problem, but the viguy prompt still had no guidance for triage vs. implementation, evaluating community PRs, or recognizing recurring issue patterns. Reviewed the last 4-5 days of issues (#25, #50, #71, #72, #100, #109, #143, #144, #145) and PRs (#127, #131, #136, #140, #141, #142, #147, #151, #153, #154) to identify patterns. Several community PRs were closed as non-problems, duplicates, or misdiagnoses (e.g., #136 added JSX pragmas for a scenario that doesn't occur; #131/#153/#154 were duplicates; #147 duplicated #123). The agent had no framework for catching these before investing review effort. - add "Triage vs. implementation" section after the scope constraint — gives the agent explicit permission to assess-then-decide rather than always jumping to code. defaults to triage when the triggering comment is ambiguous. - add "Evaluating community PRs" section with concrete quality signals: missing issue link, duplicate detection, root cause mismatch, vacuous tests (tests that pass without the fix), unrelated drive-by changes, and LLM-generated description boilerplate. includes tone guidance for community-facing comments. - add "Known issue patterns" table encoding the 6 most commonly reported root causes (RSC/SSR environment boundary, jsx-runtime CJS/ESM interop, missing shim exports, routing regex, package manager detection, immutable headers). saves re-investigation time when the same root cause gets reported again. - add duplicate PR check as step 3 in "Before starting work" — the agent now explicitly checks for existing open/closed PRs addressing the same issue before starting implementation. - add "Response structure" section near the end (recency placement) enforcing assessment-first output: assessment, evidence, then exactly one recommendation (implement/close/needs-info/defer). prevents jumping to implementation on a misdiagnosed problem. Prompt structure follows Anthropic best practices: highest-priority behavioral constraints at the top (primacy), output formatting near the end (recency), concrete examples over vague directives, and explicit negative constraints ("do not fix by adding JSX pragmas to individual files"). --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>