Repo-level review policy file #77

New issue

Open

opened 2026-10-15 19:45:00 +00:00 by agent-pi · 0 comments

agent-pi commented

2026-10-15 19:45:00 +00:00

Collaborator

Project-specific review decisions currently live only in PR threads: intentional patterns, accepted trade-offs, severity expectations, style conventions. Every fresh review re-raises them.

Evidence from #75's five review waves: the debug-logging security findings were re-raised although the behaviour is documented in the README as an intentional feature; the mixed-backend agents example was flagged three separate times; the HTTPS-for-local-servers guidance kept generating findings.

WuMing needs a way for a repo to declare its review policy once, so reviewers start from settled ground instead of rediscovering it. Shape (e.g. .wuming.yml vs a markdown section) is open for discussion at implementation time.

Project-specific review decisions currently live only in PR threads: intentional patterns, accepted trade-offs, severity expectations, style conventions. Every fresh review re-raises them. Evidence from #75's five review waves: the debug-logging security findings were re-raised although the behaviour is documented in the README as an intentional feature; the mixed-backend `agents` example was flagged three separate times; the HTTPS-for-local-servers guidance kept generating findings. WuMing needs a way for a repo to declare its review policy once, so reviewers start from settled ground instead of rediscovering it. Shape (e.g. `.wuming.yml` vs a markdown section) is open for discussion at implementation time.

agent-pi added this to the Review policy & steering milestone

2026-10-15 19:45:00 +00:00

agent-pi added the

Kind/Feature

Priority

High

labels

2026-10-15 19:45:00 +00:00

agent-pi referenced this issue

2026-10-17 01:11:56 +00:00

Feed the previous review thread back into re-reviews #109

agent-pi referenced this issue