Code Ownership Map skill for Claude and Codex

Code Ownership Map as an AI skill. It asks for Repository layout, Ownership evidence, Teams and people and 2 more, then does the rest. Free to install in…

Install it once and Claude or Codex runs it for you. When your request matches, your AI loads the skill, asks for anything it is missing, and works through the template itself. Prefer to fill it in by hand? See the full prompt template.

Download the skill (.zip) · View SKILL.md

When it is used

Use when a repository has no clear owners per directory and reviews, pages or questions keep landing on the wrong person. Do not use for assigning people to a sprint or drawing an org chart. Related topics: coding, business.

What it will ask you for

• Repository layout (longer free text)
• Ownership evidence (longer free text)
• Teams and people (longer free text)
• Time window for activity (choose one: Last 3 months, Last 6 months, Last year, All history)
• Include dependencies (choose one: Yes, No)

How it works

1. Split the repository into areas of a size one team could own, and list each with its path so every file falls under exactly one area.
2. Record the declared owner for each area from the ownership evidence, and write none where the evidence is silent.
3. Compare declared owners with recent commit and review activity inside the chosen window, so each area has a real owner or an explicit gap.
4. Label every area Clear, Disputed, Shared or Orphaned using the stated rules and attach a one-line risk.
5. Propose the three ownership-file edits that resolve the most ambiguity, each naming the path and the suggested owner.

What you get

A table of areas with declared owner, real owner, status and risk, then the orphaned and disputed areas with suggested owners, then three concrete ownership-file edits.

What it watches out for

• Treating the top committer as the owner when they only reformat or bump versions, which hides the person who understands the design.
• Trusting a stale ownership file that still names someone who left, so alerts keep routing to nobody.
• Mapping at file level, which produces hundreds of rows no one reads instead of a handful of areas someone can claim.

How to install

Claude.ai and the Claude desktop app

1. Download the skill .zip.
2. Open Settings, then Capabilities, and find Skills.
3. Choose Upload skill and select the .zip.
4. Ask Claude for help with the task. It loads the skill when your request matches.

Claude Code

1. Download the skill .zip.
2. Unzip it into ~/.claude/skills/ (or .claude/skills/ inside a project).
3. Start a new session. Claude Code loads the skill when your request matches.

Codex

1. Download the skill .zip.
2. Unzip it into ~/.agents/skills/ (or .agents/skills/ inside a project).
3. Codex picks it up on its own. Type $ and the skill name to use it, or just ask for the task.

Cursor

1. Download the Cursor rule (.mdc).
2. Save it in .cursor/rules/ inside your project.
3. Cursor's agent applies the rule when your request matches its description.

AGENTS.md (Codex, Cursor, and other coding agents)

1. Copy the AGENTS.md section.
2. Paste it into AGENTS.md at the root of your repository, creating the file if needed.
3. Coding agents that read AGENTS.md follow it when your request fits.