Re:GitHub Ponders Kill Switch for Pull Requests to Stop AI Slop
by dkargatzis on Monday February 09, 2026 @05:13PM
(#46952255)
A PR kill switch is tempting, but it also kills collaboration.
What we’re building instead looks at review-time signals rather than hard blocks. It surfaces why a PR is expensive to review:
- diff surface vs scope
- files touched vs CODEOWNERS boundaries
- changes on auth / validation / error-handling paths
- PRs that pass CI by mocking or bypassing real execution paths
Nothing is auto-rejected by default, the goal is to reduce low-context PRs before a maintainer has to reconstruct intent manually.
There’s a preview at https://watchflow.dev if you want to see how this behaves on real PRs. Open to feedback on which signals actually help in practice.
What we’re building instead looks at review-time signals rather than hard blocks. It surfaces why a PR is expensive to review:
- diff surface vs scope
- files touched vs CODEOWNERS boundaries
- changes on auth / validation / error-handling paths
- PRs that pass CI by mocking or bypassing real execution paths
Nothing is auto-rejected by default, the goal is to reduce low-context PRs before a maintainer has to reconstruct intent manually.
There’s a preview at https://watchflow.dev if you want to see how this behaves on real PRs. Open to feedback on which signals actually help in practice.