CODEOWNERS Generator and Validator
Paste a public repository link and Scopy validates its existing CODEOWNERS file or proposes one from the repository's own structure and contributors.
Inspect a public repository
Scopy checks for an existing CODEOWNERS file first. If one exists, it gets validated; otherwise Scopy proposes one from the repository's top-level directories and contributors.
Generated CODEOWNERS
Inspect a public repository to generate or validate its CODEOWNERS file.
How should CODEOWNERS rules be reviewed?
CODEOWNERS uses the last matching rule for a path, so rule order is part of the policy. A syntactically valid file can still leave sensitive paths without the intended reviewer or reference teams that lack repository access.
Paste a repository link and Scopy reads its public structure through GitHub's API: if a CODEOWNERS file already exists at .github, the root, or docs, it gets validated for the mistakes GitHub silently tolerates — malformed owner handles, duplicate patterns, escaping problems, and rules that can never match. If none exists, Scopy proposes ordered ownership rules from the repository's top-level directories and its most active contributors, which you can adjust before downloading.
Ownership files earn their keep during incidents and departures. When the person who wrote the payment integration leaves, CODEOWNERS is often the only machine-readable record of who should review that area next. Keep it accurate the same way you keep tests green — update it in the same pull request that moves the code.
This tool checks structure and common pattern problems from public repository data. Commit the file to .github, the repository root, or docs, then confirm resolution and branch-protection behavior in GitHub.
Related reading: Code review best practices for fast-moving teams.
Frequently asked questions
- Does this tool access my private repository?
- No. It only reads public repositories through GitHub's unauthenticated API — directory listings, an existing CODEOWNERS file, and contributor logins. For a private repository, use the manual tab to paste paths or an existing file instead; that runs entirely in your browser.
- Why are my CODEOWNERS rules not triggering review requests?
- The usual causes: the file is not on the default branch, a later rule overrides your rule because last match wins, the referenced team lacks write access to the repository, or the pattern does not actually match the path. The validator here catches pattern and ordering problems; access problems only GitHub can confirm.
- Does CODEOWNERS enforce anything by itself?
- On its own it only auto-requests reviewers. Enforcement comes from branch protection: enable 'Require review from Code Owners' on the protected branch to make the ownership rules blocking.
- Are the suggested owners accurate?
- They are a starting point, not a final answer. Suggested owners come from the repository's most active public contributors, which is not the same as its current team structure. Always replace them with real team handles before committing the file.
Try Scopy AI on your next pull request
Accurate, open-source AI code reviewer that understands your project. Self-host it or start in the cloud.