forensic-knowledge-mapping

Analyze Git history to identify single-owner files and calculate truck factor.

3|2|Updated Oct 27, 2025
One-click install
npx skills add https://github.com/AlabamaMike/forensic-skills --skill forensic-knowledge-mapping
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: forensic-knowledge-mapping
Source: https://github.com/AlabamaMike/forensic-skills/tree/main/.claude/skills/forensic-knowledge-mapping
Command: npx skills add https://github.com/AlabamaMike/forensic-skills --skill forensic-knowledge-mapping

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill maps code ownership from Git history to identify knowledge silos and calculate the truck factor, helping teams anticipate risks when key developers depart.

Core Features & Use Cases

  • Compute ownership percentages across files from commit history to reveal concentration.
  • Identify single-owner files (>80% commits by a single contributor) and calculate truck factor.
  • Cross-reference with hotspots to surface high-risk areas and plan knowledge transfer.
  • Provide actionable mitigation strategies based on research-backed thresholds.

Quick Start

To begin, run the ownership analysis (e.g., ownership-analyzer.py) over the last 12 months to generate a knowledge map, review primary owners, and plan knowledge transfer.

Frequently Asked Questions about forensic-knowledge-mapping

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

FAQPage Schema
How do I calculate the truck factor for my codebase using Git history?

To calculate the truck factor, this skill analyzes Git commit history to compute ownership percentages across files and identify single-owner files where over 80% of commits are from one contributor.

What is code ownership analysis and how does it identify knowledge silos?

Code ownership analysis maps commit history to reveal ownership concentration, identifying single-owner files and knowledge silos where critical codebase knowledge is held by only one developer.

How can I reduce bus factor risk in my engineering team through succession planning?

You can reduce bus factor risk by analyzing ownership distributions to surface high-risk single-owner files, then applying research-backed mitigation strategies to plan targeted knowledge transfer and onboarding.

Can I detect single-owner files and high-risk code hotspots across my repository?

Yes, you can detect single-owner files by analyzing Git history for commit concentration, then cross-reference those files with code hotspots to surface areas requiring immediate knowledge transfer.

Does this ownership analysis work for large codebases over a specific time period?

The ownership analysis works across large codebases by processing Git history over a defined time range, such as the last 12 months, to generate a comprehensive knowledge map of file ownership distributions.

What research-backed thresholds are used to flag single-owner files for knowledge transfer?

The analysis uses a research-backed threshold where any file with over 80% of commits from a single contributor is classified as a single-owner file, flagging it for immediate knowledge transfer mitigation.