1
    🚌 Bus Factor Report

    🚌 Bus Factor Report

    by JustHandled Labs

    Find where knowledge is dangerously concentrated in a codebase. From your git history it flags the files only one person has ever touched, the high-churn files with a single owner, authors who own too much of the codebase, and the repo's overall truck factor. The catchy question with a real answer: what breaks if a key person leaves.

    Updated Jun 2026
    Security scanned
    Cursor

    $12

    Β· or 60 credits

    30-day refund guarantee

    Secure checkout via Stripe

    Included in download

    • Identify critical files maintained by only one developer
    • Calculate the team's truck factor score for risk management
    • file_read, terminal automation included
    • Ready for Cursor
    • Instant install

    Sample input

    Analyze this git log output and tell me our bus factor risk and which files are most vulnerable: [git log text provided]

    Sample output

    Bus Factor Report

    Estimated Truck Factor: 2

    High-Risk Files (Single Owner):

    • /core/auth-engine.js (84 commits, Owner: @jdoe)
    • /utils/crypto-helper.py (42 commits, Owner: @jdoe)

    Author Ownership:

    • @jdoe: 68% (Extreme Concentration)
    • @asmith: 22%
    • @rlee: 10%

    About This Skill

    Detect Knowledge Concentration Risk

    The Bus Factor Report skill helps developers and engineering managers identify "knowledge silos" within their repositories. By analyzing git history data, it pinpoints files that have only ever been touched by a single contributor and identifies authors who own a disproportionate share of the codebase.

    How it works

    This skill processes standard git log output to calculate ownership metrics. It scans for single-owner files (BFR001) and flags high-risk componentsβ€”those frequently changed but only understood by one person (BFR002). It provides a high-level summary including an estimated truck factor and per-author ownership percentages.

    Why use this skill?

    • Risk Mitigation: Proactively identify critical systems that would be unsupported if a key developer left the project.
    • Onboarding Strategy: Determine exactly which files require pair programming or documentation to spread knowledge.
    • Data-Driven Insights: Move beyond "gut feelings" about code ownership with concrete authorship stats.
    • Non-Intrusive: It parses text logs rather than requiring direct shell access, making it safe for use in restricted environments.

    Output format

    The skill generates a structured report identifying specific high-risk files, author concentration percentages, and an overall Bus Factor score, accompanied by remediation suggestions.

    Use Cases

    • Identify critical files maintained by only one developer
    • Calculate the team's truck factor score for risk management
    • Detect authors with excessive ownership share in the codebase
    • Generate remediation advice for spreading technical knowledge

    Reviews

    No reviews yet - be the first to share your experience.

    Only users who have downloaded or purchased this skill can leave a review.

    Security Scanned

    Passed automated security review

    Permissions

    Read Files
    Terminal / Shell

    File Scopes

    bus-factor-report/**
    **/git-log.txt
    **/*.gitlog
    --stdin

    Read-only on the provided history text. The over-concentration share and truck-factor threshold are configurable. Reads no environment variables.

    Tags

    git
    devops
    project-management
    code-analysis
    risk-assessment

    Works with any agent that can run a git command and a local Python script (Claude Code, Cursor, Codex CLI, and other SKILL.md-compatible agents). Standard library only, no install step. It parses the git-log output you pipe in; it does not run git itself or call the network.

    Creator

    JustHandled Labs

    JustHandled Labs builds focused agent skills for the work nobody wants to do by hand. Each one is a single repeatable job done well: catching the security and data mistakes that quietly ship, keeping docs and tests honest, gating the commands an agent is about to run, sharpening writing, and handling the founder chores around launches, outreach, and brand setup. Not generic AI productivity. Specific workflows that are easy to run, review, and repeat. Maintained by H.J. Westerfield, with a background in communications, editing, project coordination, customer support, and practical AI systems. Tools for people who want useful automation without theatrical complexity.

    Frequently Asked Questions

    Learn More About AI Agent Skills

    More Premium Skills

    Multi-Agent Orchestration Master Library

    Transform Claude Code into a coordinated multi-agent system. Battle-tested tmux orchestration patterns, YAML task queues, event-driven communication, and parallel worker management for 8+ agents.

    $157 installs

    designing-hybrid-context-layers

    Architects the right retrieval strategy for every query β€” teaching your agent when to use RAG, a knowledge graph, or a temporal index instead of defaulting to vector search for everything.

    $1015 installs

    consumer-motivation-analyzer

    Go beyond surface-level feedback to uncover the psychological drivers and hidden motivations behind buyer behavior.

    $199 installs

    ai-automation-qa-pack

    Professional QA & UAT documentation generator for AI automation agencies and complex agent deployments.

    $58 installs

    $12