Would five plain PR handoff lines help maintainers, or add friction?

[shihchengwei-lab]

Hi, I built a small GitHub Action called Corridor CI.

I do not review PRs, so I cannot judge whether it helps in practice.
People here do, which is why I am asking.

The idea is simple: 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.

For Agno, where PR triage already checks issue links, tests, duplicate PRs, and low context descriptions, would this help triage review boundaries, or would it mostly add friction?

I would appreciate any maintainer perspective on whether this kind of receiving side check matches a real pain.

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