Route agent PRs to the right humans with CODEOWNERS

What it does

A CODEOWNERS file maps file paths to the people or teams responsible for them. Combined with required code-owner review on a protected branch, every pull request automatically requests review from the right human. For agent-authored PRs, this is the routing layer between automation and accountability.

Steps

1. Create .github/CODEOWNERS in the repo. Anyone with write access can create or edit it.

2. Assign by path, broad to specific:

   • @org/core-team

   /payments/ @org/payments-team

3. In the branch protection rules, require review from code owners. A PR touching payments cannot merge without the payments team.
4. Keep the teams small and real. A code owner who never reviews is a rubber stamp. Rotate the responsibility.

Checks

• Open a test PR touching a scoped path and confirm the right team gets requested.
• Audit CODEOWNERS for departed people and dead teams regularly. Stale owners silently block or silently wave through.

GitHub's docs describe using a CODEOWNERS file to define the individuals or teams responsible for code in a repository, and branch protection can require review from a designated code owner. Source: https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners