git history forensics auditor

    1

    Excavate git history to detect revert loops, calculate Bus Factor risk, and generate safe recovery commands.

    $5.99

    /mo

    Subscription · cancel anytime

    Secure checkout via Stripe

    • Always the latest version
    • Delivered live to your agent via MCP
    • Cancel anytime, access ends at period end
    Security scanned

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIDeepSeekDeepSeekMuseMuse+22 more

    git history forensics auditor

    Example session with this skill installed

    Audit this log for stability
    e5f6g7h|dev_a|2027-01-01|feat: ui
    f6g7h8i|dev_a|2027-01-02|Revert "feat: ui"
    g7h8i9j|dev_b|2027-01-03|hotfix: fix ui crash
    h8i9j0k|dev_a|2027-01-04|wip: fix again

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

    I have analyzed the provided git log history for the main branch. The audit identifies a volatile commit pattern with high contributor concentration.

    Git History Forensics Audit Report

    MetricValue
    Total Commits4
    Reverts Detected1
    Hotfixes Detected1
    WIP Commits1
    Bus Factor1 (dev_a = 75% share)
    Release Stability Score47 / 100
    StatusVOLATILE_HOTFIX_LOOP

    Forensic Findings

    High Churn: The presence of a revert followed immediately by a hotfix and a WIP commit suggests an unstable feature rollout.

    Knowledge Concentration: dev_a authored 75% of the recent history, indicating a significant Bus Factor risk for this module.

    Integrity Warning: WIP commits detected in the target branch history. These should be squashed before further releases.

    Safe Recovery Commands

    To inspect the revert and prepare a clean state without a force-push:

    
    # Inspect the impact of the revert
    git show --stat f6g7h8i
    
    # Stage a revert of the revert to restore the feature safely for local testing
    git revert --no-commit f6g7h8i
    

    Next steps

    1. Run git squash on the WIP commits to clean up the branch history.
    2. Conduct a peer review with dev_b to reduce the Bus Factor concentration held by dev_a.
    3. Verify the hotfix: fix ui crash logic against the original feat: ui requirements.
    $5.99/mo

    Subscription · always the latest version

    • Secure checkout via Stripe
    • Cancel anytime
    • Delivered live via MCP

    About this skill

    Git logs are often a mess of cryptic messages and emergency hotfixes that hide the true health of a codebase. This skill parses raw git history to detect revert loops, calculate Bus Factor risk, and generate safe recovery paths without destructive force-pushes.

    What it does

    • Stability scoring calculates a 0 to 100 Release Stability Score based on reverts, hotfixes, and WIP churn.
    • Bus Factor analysis identifies single-contributor knowledge concentration risks where one person owns over 50% of the commits.
    • Revert loop detection flags emergency rollbacks and hotfix patterns that indicate unstable release cycles.
    • Safe recovery generation provides non-destructive git revert or git bisect commands for incident response.
    • Narrative reconstruction transforms raw commit hashes and timestamps into a readable audit of recent engineering activity.

    How it works

    1. Provide raw log data by piping git log output (standard or custom formats) into the git_log_raw argument.
    2. Select an audit mode such as FULL_FORENSICS for a deep dive or BUS_FACTOR_RISK for team health checks.
    3. Analyze findings including the Stability Score and detected churn hotspots.
    4. Execute recovery using the suggested non-destructive Git commands provided in the output.

    Frameworks & tools

    This tool works with any repository using Git. It consumes raw text from git log and is compatible with standard CLI output or custom formats like hash|author|date|message.

    Why this beats prompting it yourself

    Standard LLMs often hallucinate commit hashes or suggest dangerous force-push commands when asked for Git help. This skill uses deterministic formulas for stability and Bus Factor, ensuring recommendations prioritize repository integrity over quick fixes.

    Use cases

    • Incident post-mortems to trace the sequence of reverts and hotfixes during a production outage.
    • Onboarding audits to see which developers hold the most context in a specific branch.
    • Pre-release checks to flag "WIP" or "fixup!" commits that should have been squashed.
    • Recovery planning to generate safe rollback commands during high-pressure deployments.

    Known limitations

    This skill does not execute live Git commands or perform force-pushes. It does not scan source code for security vulnerabilities.

    Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for LLM Ops.

    Does not execute live Git commands. Does not perform security vulnerability scanning. Requires raw git log text as input.

    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

    Free to use

    No account required to browse

    Trust & safety

    Security scan

    Security scan passed 1 day ago

    Software
    Git

    Permissions

    Terminal / Shell
    Read Files
    Listed1 day ago

    What's inside

    Frequently Asked Questions

    This skill identifies 'revert loops' (patterns of rollbacks followed by hotfixes) and 'Bus Factor' risks, where a single developer holds too much knowledge, helping teams prevent outages and technical debt.

    Yes, it is designed to be framework-agnostic; as long as you can pipe the output of `git log` into the tool, it can analyze any repository regardless of the programming language.

    The skill identifies the precise commit hashes needed for recovery and generates non-destructive `git revert` or `git bisect` sequences, ensuring you never have to use a risky `force-push`.

    You receive the specialized Git Forensics skill profile, a guide on optimal `git log` formatting for deep audits, and lifetime access to any logic updates or stability scoring improvements.

    No, this skill is a read-only auditor; it analyzes provided log data and suggests commands for you to review and run manually, ensuring complete human-in-the-loop control.

    New in LLM Ops