skills.rest
JaimeJunr
JaimeJunrCOMMUNITY
Explore all skills by this author →
GitHub

security-ownership-map

Generate a people-to-files ownership topology with risk hotspots from git history.

2|Updated Apr 11, 2026
Search Tags:#security#ownership#git-history#codeowners#bus-factor#cochange#graph-export
One-click install
npx skills add https://github.com/JaimeJunr/context-mode --skill security-ownership-map-jaimejunr
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: security-ownership-map
Source: https://github.com/JaimeJunr/context-mode/tree/main/.claude/skills/security-ownership-map
Command: npx skills add https://github.com/JaimeJunr/context-mode --skill security-ownership-map-jaimejunr

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires networkx, and includes scripts (resource) and references (resource) components.

What problem does it solve?

Analyze git history to generate a security ownership topology (people-to-files) and identify bus factor and sensitive-code hotspots, enabling governance and risk awareness across codebases.

Core Features & Use Cases

  • Build a bipartite graph of people and files from git history and compute ownership risk and hotspot detection.
  • Export outputs for graph databases and visualization (CSV/JSON), including a co-change graph to reveal how files move together.
  • Detect sensitive code hotspots and ownership drift to inform CODEOWNERS validation and risk scenarios.

Quick Start

Run the build_ownership_map script against your repository to generate the ownership maps and summary in the output directory.

Frequently Asked Questions about security-ownership-map

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I analyze git history to calculate bus factor and code ownership risk?▼

To analyze git history for bus factor and code ownership risk, run the build_ownership_map script against your repository to generate a people-to-files bipartite graph and summary outputs.

What is a co-change graph and how does it reveal ownership drift?▼

A co-change graph reveals how files move together in git commits. Detecting sensitive code hotspots through this mapping highlights ownership drift where governance and risk management lack visibility.

Can I export git ownership topology to Neo4j or Gephi for visualization?▼

Yes, you can export the git ownership topology to Neo4j or Gephi. The Skill produces CSV and JSON graph artifacts, including optional graphML files specifically for Neo4j and Gephi visualization.

Does the ownership mapping tool support configurable time windows and exclusions?▼

Yes, the ownership mapping tool supports configurable time windows and exclusions. This allows you to bound the git history analysis and focus the ownership topology on specific project periods.

Do I need networkx to build the security ownership map from git history?▼

Yes, you need networkx to build the security ownership map. It is a required dependency for generating the bipartite graph of people and files and computing the ownership risk topology.

Related Skills

Explore More Software Engineering Skills→
alangebalangeb

git-advanced

Perform Git bisecting, cherry-picking, and log analysis operations locally.

Community
Advanced
wosnatwosnat

cypher-queries

Run Cypher queries against a Neo4j knowledge graph using prepared templates.

Community
Advanced
alanharrryy-wqalanharrryy-wq
2

security-ownership-map

Analyze git history to map file ownership and compute bus-factor metrics.

Community
Advanced
Intense-VisionsIntense-Visions
18

harness-hotspot-detector

Analyze Git history and churn data to rank structural risk hotspots.

Official
Advanced