This has become our biggest bottleneck. I added a step in our CI that evaluates the diff to determine if it can go through without human review or not. It determines this by working out if we are changing code in the critical path, adding a new dependency, adding a new design…
I added a proposal here to ensure agents (and human devs) write compliant PRs in the first place.
https://github.com/dev-null-sh/dev-null.sh/issues/1011
Personally, in my own work. I start with skills so agents can't write anything that's not first detail spec'd or ratified…
GitHubProposal: a Boost skill that walks agents through preparing a pull request · Issue #1011 · dev-null-sh/dev-null.shProblem There are hundreds of PRs in mere days. For the maintainers life is going to get hectic! The PR templates and .ai/guidelines/github.pull-requests.blade.php (#954) say what a good PR needs, ...