idea: prs should be opened against a repo and any engineer can submit prompts that start a codex session with the goal to either validate certain tests or answer pointed questions about specific code
the responsibility to ensure a codex session can spin up and run unit/potentially integration tests along with enough information in the PR should be placed on the pr creator
this shifts the burden of review back on the creator by allowing peers with tacit knowledge to quickly validate a hypothesis without needing those engineers to dive extremely deep into the pr every time
in essence the goal is to drive velocity on verifiable coverage, and this incentivizes this by reducing the barrier to entry such that even drive by comments become helpful
objection: reviewers won't trust the review agent's answer
response: I disagree, we run a pretty thorough agent internally that gets used to debug problems and we can pretty easily guide it due to our system level knowledge and also catch when its out of its depth
objection: this doesn't handle code quality
response: yes I agree, but code quality should be objective measures for the most part supported by style guides, linters, and scoped agents anyways