Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIDeepSeekDeepSeekMuseMuse+22 more

    Git History Hotspots

    1

    Git history analysis: shows churn hotspots, files owned by one person (bus factor) and files that always change together.

    $5

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    Git History Hotspots

    Git History Hotspots

    Example session with this skill installed

    /git-hotspots .

    • Read your context and instructions
    • Compiled the git history hotspots

    Illustrative. The history is invented (three made-up authors and files); the report below is what the script prints for it.

    GIT HOTSPOTS (61 commits, 64 files, 3 authors, 2026-01-03 to 2026-03-27)
    
    1. Most changed files (2 or more commits; lines added and removed, authors, last change)
       src/billing/invoice.py                           23 commits  +620 -328  2 authors  last 2026-03-21
       tests/test_invoice.py                            20 commits  +472 -360  2 authors  last 2026-03-26
       src/api/routes.py                                15 commits  +515 -291  2 authors  last 2026-03-25
       src/billing/tax.py                                8 commits  +138 -226  2 authors  last 2026-03-27
       src/api/schemas.py                                8 commits  +190 -128  2 authors  last 2026-03-25
       src/core/config.py                                6 commits  +210 -81  2 authors  last 2026-03-13
       README.md                                         4 commits  +124 -104  2 authors  last 2026-02-23
    
    2. Changed mostly by one person (at least 80 percent of 5 or more commits)
       src/billing/invoice.py                           23 commits  Ana 20 of 23 (87%)
       tests/test_invoice.py                            20 commits  Ana 17 of 20 (85%)
       src/billing/tax.py                                8 commits  Ana 7 of 8 (88%)
       src/core/config.py                                6 commits  Chi 5 of 6 (83%)
    
    3. Files that change together (3 or more commits; the percent is the share of the less-changed file's commits)
       src/billing/invoice.py + tests/test_invoice.py  together in 16 commits (80%)
       src/api/routes.py + src/api/schemas.py  together in 6 commits (75%)
       src/billing/invoice.py + src/billing/tax.py  together in 3 commits (38%)
    
    Left out of part 3: 1 commit(s) that touch more than 50 files (mass edits tell nothing about what belongs together).
    Limits: this counts commits, not bugs. A file changes often because it is busy, central or badly structured, and a log cannot tell which. Renames count as a delete and a new file, so history before a rename is lost. Author names are taken as written, so one person under two names counts twice, and squash merges hide who wrote what. Lock files and minified files are ignored by default. A short list is not a sign of healthy code.
    

    Next steps

    • Open the top hotspot, check its size and its tests, and read its last few commit messages before deciding anything.
    • Pick one file from the one-person list and have a second person review or document it.

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

    About this skill

    See where a codebase hurts before you open a single file. The skill runs one read-only git log command and a local script that turns the history into three lists: the files that change in the most commits (with lines added and removed, number of authors and last change), the files that are mostly one person's work, and the pairs of files that tend to change together. Lock files and minified files are ignored, and mass-edit commits are left out of the change-together list. A reference file explains how to read each list and what to check next: tests, size, review, hidden dependencies.

    What it reads and writes: the history of the repository you name, through one read-only git log command (or a log file you saved); it writes nothing, commits nothing and changes no file. The script itself never runs git and only reads the text it is given. No network connection, no environment variables, nothing to install besides Python and git.

    Honest limits: it counts commits, not bugs or quality. A file changes often because it is busy, central or badly structured, and a log cannot tell which. Renames count as a delete and a new file, so history before a rename is lost. Author names are taken as written (one person under two names counts twice), squash merges hide who wrote what, and the author is who committed, not who understands the code today. Needs Python 3.9+ and git.

    Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Testing & Debugging.

    Needs Python 3.9+ and git. Counts commits, not bugs or quality. Renames reset a file's history, one person under two names counts twice, squash merges hide who wrote what, and the author is who committed, not who understands the code today.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before buying a skill.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 15 days ago

    Software
    PythonGit

    Permissions

    Terminal / Shell
    Read Files

    File Scopes

    <the
    repository
    history
    or
    log
    file
    you
    name>

    Runs one read-only git log command and a local script that reads only that text; it commits nothing, writes no file, makes no network connection and reads no environment variables.

    Listed15 days ago
    Updated13 days ago

    What's inside

    Frequently Asked Questions

    No. The skill runs one read-only git log command and a local script. It commits nothing, writes no file and makes no network connection.

    The whole history by default. For very large repositories add -n 5000 to the git command, or use --since-days N for a recent window (counted back from the newest commit in the log).

    No. The report counts commits. A file changes often because it is busy, central or badly structured, and a log cannot tell which. The reference file gives checks for each case.

    Lock files (package-lock.json, yarn.lock, pnpm-lock.yaml, poetry.lock, Pipfile.lock, Cargo.lock, go.sum, composer.lock, Gemfile.lock) and minified js and css by default. Add --ignore GLOB for more, or --no-default-ignore to keep everything.

    New in Testing & Debugging