Owner Map - who actually knows this code

Paste a git-history export and see who holds the recent knowledge of every file: recency-weighted ownership share, bus factor, orphaned and stale sensitive paths, and a CODEOWNERS reality check - all measured in your browser, free, without the log ever leaving the page. Then three lanes over that measurement: an ownership risk review with a generated CODEOWNERS draft, a dated knowledge-transfer plan for the paths one person holds, and a split of your in-flight change set into pull requests that each need the fewest reviewer groups. Derived from three published agent skills: @openai/security-ownership-map, @sickn33/git-pr-workflows-onboard and @nvidia/mcore-split-pr.

Every public app is built from a security-scanned skill and must pass a clean scan — skill and frontend — before it can be listed. Have a skill of your own? Turn it into an app — or read the step-by-step walkthrough.