Would a "declare your review boundary" check help here?

[shihchengwei-lab]

Hi, I built a small GitHub Action called Corridor CI.
I do not review PRs day to day myself, so I have no way to judge whether it helps in practice.
People here do, which is why I am asking.

The idea is: a non-trivial PR must carry five plain lines in its body:

Decision: #123
Scope: pkg/parser/, tests/parser/
Review first: pkg/parser/links.py
Verified: pytest tests/parser
Risk: low

CI checks that the diff stays inside the declared Scope and that Review first is a changed file.
It does not judge code quality. It does not care who or what wrote the code.
A red check means information is missing, not that the code is bad.
Tiny fixes can be exempt.

The bet behind it: review attention is the scarce resource, and the cheapest place to protect it is the receiving end, before review starts.

If you review PRs here: would a check like this help triage, or would it mostly add friction?
Where would it break down for a project like OpenCRE, with waves of first-time contributors?

Repo: https://github.com/shihchengwei-lab/corridor-ci

No external adopters yet. Any perspective is appreciated, including that it would not help.