Code Ownership Map
By Jamie · Published · Updated
Shows who owns each part of a codebase and where nobody does, so reviews and incidents reach a person instead of a shrug.
Prompt template
## Code Ownership Map Build an ownership map for this codebase. - Repository layout: [textarea: Paste the top two levels of the directory tree] - Ownership evidence: [textarea: CODEOWNERS contents or git shortlog output or team notes] - Teams and people: [textarea: Names and what each group is responsible for] - Time window for activity: [dropdown: Last 3 months, Last 6 months, Last year, All history] - Include dependencies: [toggle: Yes, No] Work area by area, not file by file. For each top-level area, name the declared owner from the evidence, then compare it with who actually commits and reviews there. Mark each area as Clear, Disputed (declared and real owners differ), Shared (three or more active authors with no lead), or Orphaned (no declared owner and no recent activity). Treat a departed person as no owner. Present a table with area, declared owner, real owner, status and risk, then list the orphaned and disputed areas first with a suggested owner and the reason. When dependencies are included, add the vendored or third-party code nobody maintains. End with the three smallest edits to the ownership file that would remove the most ambiguity.