SWE Ownership Risk Map

What This Skill Does

Use this skill to identify where a repository is most exposed to ownership risk, not to build a people directory.

The goal is to produce a ranked map of surfaces that are likely to become fragile because of:

• concentrated commit ownership
• high churn with few distinct contributors
• unclear or missing CODEOWNERS coverage
• low test density near important code paths
• stale or orphaned modules, scripts, or configs
• recent turnover or repeated handoffs in the same surface

The output should be suitable for scheduled maintenance: short, repeatable, and easy to compare across runs.