analyze-knowledge

Analyze git commit history to recommend pull request reviewers and assess knowledge concentration risk.

9|Updated Mar 22, 2026
One-click install
npx skills add https://github.com/paultyng/skill-issue --skill analyze-knowledge
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: analyze-knowledge
Source: https://github.com/paultyng/skill-issue/tree/main/skills/analyze-knowledge
Command: npx skills add https://github.com/paultyng/skill-issue --skill analyze-knowledge

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill eliminates the guesswork of identifying who has deep expertise in specific code areas, streamlines pull request review assignment beyond GitHub's default suggestions, and helps teams proactively address knowledge concentration risks that create bus factor vulnerabilities.

Core Features & Use Cases

  • Reviewer Suggestion: Automatically rank contributors by their weighted, recent contributions to changed files to recommend the most qualified PR reviewers, excluding the PR author.
  • Knowledge Distribution Analysis: Map expertise across code directories, calculate lottery factor and concentration percentages to flag high-risk areas where knowledge is held by too few people.
  • Use Case: A team onboarding to a legacy codebase can use this skill to quickly identify who to consult for specific modules, or a tech lead can use it to assess bus factor risk before a key contributor goes on leave.

Quick Start

Use the analyze-knowledge skill to recommend the top 3 reviewers for your current pull request and identify any high-risk knowledge concentration in the modified code areas.

Frequently Asked Questions about analyze-knowledge

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

FAQPage Schema
How do I find the best PR reviewers from git history?

To find PR reviewers from git history, this skill analyzes commit logs to rank contributors by their weighted, recent changes to specific files, automatically excluding the pull request author from suggestions.

What is the bus factor and how is code expertise calculated from git commits?

Bus factor calculations from git commits map individual code expertise across directories by applying weighted recency scoring, prioritizing recent contributions to assess knowledge concentration and identify high-risk areas held by too few people.

Can I analyze code knowledge distribution in a local git repository?

You can analyze code knowledge distribution in a local git repository by calculating lottery factor and concentration percentages across code directories to flag areas where critical knowledge is held by too few contributors.

Does the code expertise analysis support mailmap for author normalization?

Yes, the code expertise analysis supports mailmap for author normalization, ensuring that multiple commit identities belonging to the same developer are consolidated when calculating weighted recency scores for reviewer suggestions.

How do I identify high-risk knowledge concentration areas before a key contributor goes on leave?

To identify high-risk knowledge concentration areas before a contributor leaves, this skill maps expertise across code directories and flags vulnerable modules where knowledge concentration percentages indicate a low bus factor.

What is the best way to onboard a team to a legacy codebase using git history?

The best way to onboard a team to a legacy codebase using git history is to analyze commit logs to identify individuals with deep expertise in specific modules, pinpointing exactly who to consult for targeted code areas.