Works with the AI tools you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+22 more

    Git History Analyzer

    1

    Extract engineering metrics, bus factor risks, and code hotspots from git history.

    $4.99

    Secure checkout via Stripe

    30-day refund guarantee

    Converts to your local currency at checkout

    Security scanned
    Git History Analyzer

    Git History Analyzer

    Example session with this skill installed

    Run a git history analysis for the last 6 months on the src/ directory and identify hotspots and bus factor risks.

    • Read your context and instructions
    • Compiled the git history analyzer
    • Generated the data export

    I have analyzed the git history for src/ over the past 6 months. The analysis processed 452 commits from 8 authors, identifying 3 high-risk hotspots and 2 files with a bus factor of 1.

    Repository Health Report (src/)

    MetricValueRisk Level
    Top Hotspotsrc/auth/provider.tsHigh (42 changes)
    Highest Churnsrc/api/endpoints.tsMedium (+1,200 / -850)
    Bus Factor (Total)3Medium
    Temporal Couplingsrc/utils/db.ts & src/models/user.ts85% correlation

    Key Findings

    Knowledge Silo: src/auth/provider.ts is 92% owned by dev-alpha. If this contributor is unavailable, the authentication logic has zero redundancy.

    Architectural Debt: src/utils/db.ts and src/models/user.ts are coupled. 17 out of 20 commits to the utility file required a simultaneous change to the user model, suggesting a leaky abstraction.

    Bug Hotspot: src/api/endpoints.ts shows high churn with a fix-to-feature commit ratio of 0.6, indicating frequent regressions.

    Next steps

    • Review the insights/bus_factor.csv for a full list of single-owner files.
    • Consider a pair-programming session for src/auth/ to distribute knowledge.
    • Refactor src/utils/db.ts to decouple it from the user model.

    bus_factor.csv

    CSV · data export

    Generated

    Example file from a real run - the skill writes it into your workspace.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Engineering managers and leads often struggle to identify technical debt and bus factor risk until a developer leaves or a deployment fails. This skill mines git logs to transform raw commit history into actionable repository health metrics.

    What it does

    • Hotspot detection identifies files with high change frequency that are likely candidates for refactoring.
    • Bus factor analysis calculates line ownership per file to surface single-point-of-failure risks.
    • Temporal coupling finds hidden dependencies by tracking files that are frequently committed together.
    • Churn tracking measures the ratio of lines added versus deleted to monitor codebase stability.
    • Author distribution maps knowledge silos across directories based on commit volume and recency.

    How it works

    1. Targeting specifies the time range or specific subdirectories to analyze within the local repository.
    2. Extraction runs the analysis engine to parse git logs, blame data, and commit metadata.
    3. Reporting generates a Markdown summary of hotspots, risks, and activity trends.
    4. Data Export produces CSV files for deeper analysis in external spreadsheet or visualization tools.

    Frameworks & tools

    This skill utilizes git CLI, python3, and standard shell utilities to process repository metadata.

    Why this beats prompting it yourself

    Standard LLM prompts cannot access the full history of a local repository or perform complex statistical aggregations on thousands of commits. This skill automates the heavy lifting of git log parsing and applies specific logic to calculate metrics like bus factor and temporal coupling accurately.

    Use cases

    • Auditing a legacy codebase to find the most bug-prone modules for refactoring.
    • Assessing team knowledge distribution before a major organizational change.
    • Identifying hidden architectural dependencies that cause regression errors.
    • Onboarding new developers by showing them which files are high-activity hotspots.

    Known limitations

    Requires a local git repository and Python 3. Accuracy of author metrics depends on consistent git mailmap configurations.

    How to use

    Skills on Agensi run inside your AI agent. Copy the prompt, paste it into your agent, and it connects to Agensi and installs this skill for you. If a payment is needed, your agent shows it to you first.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill passes our trust checks below.

    Security scanned

    Passed our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    30-day refund

    Not a fit? Get your money back

    Trust & safety

    Security scanned

    Verified clean today

    • Passed all security checks, Safe to install

    Listedtoday

    What's inside

    Frequently Asked Questions