GitHub CODEOWNERS and Review Routing Plan
Plan ownership so the right people review changes.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
[VERIFY] is an editorial flag, not a blank to fill. Wherever the prompt shows [VERIFY], check that item against a reliable source before you use it.
Plan CODEOWNERS for a repository. Directory structure: [DIRECTORY_STRUCTURE]. Teams and people responsible for areas: [OWNERS]. Risky areas needing extra review: [RISKY_AREAS]. Team availability and holidays: [AVAILABILITY]. Write a draft CODEOWNERS file with comments, patterns and placeholder usernames, and explain the pattern rules and order of precedence in plain words [VERIFY]. Recommend how many owners per area to avoid bottlenecks, and give every owner a named backup for absence. Walk through three sample changes: one in the payments directory, one in documentation and one touching both; for each name who would be asked to review and what happens if they are away. Point out patterns that route too much to one person and suggest splitting ownership by subdirectory. Add a policy for emergency changes and a quarterly check that each owner still works on the area. This file only requests reviews; branch protection settings decide whether review is required [VERIFY]. List the risks: stale owners, patterns too broad, and slow reviews.
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.