More screenshots

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    Temporal Git Forensics — Causal Debugger & Time-Travel

    1

    Causal Git forensics, zero-dirtying time-travel state reconstruction, regression bisect pinning, and hotfix patch generator.

    $15

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    Temporal Git Forensics — Causal Debugger & Time-Travel

    Temporal Git Forensics — Causal Debugger & Time-Travel

    Example session with this skill installed

    Run temporal git forensics to diagnose why tests in test_auth.py are failing and pinpoint the offending commit.

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

    ==================================================================
    🎯 TEMPORAL GIT FORENSICS — Automated Bisect & Pinpointer

    Good Boundary: 21eadf1e | Bad Boundary: HEAD (c03bfcfa)
    Commits In Search Space: 4

      Step 1: Testing 4aeefc40 -> FAIL (Bad)
      Step 2: Testing 21eadf1e -> PASS (Good)
    ------------------------------------------------------------------
    

    💥 OFFENDING COMMIT PINPOINTED: 4aeefc4
    Subject: refactor: simplify token validation logic
    Author: Alex Developer alex@enterprise.com
    Date: 2026-10-18T00:15:20+02:00
    Impact: +2 / -3 lines across 1 file(s)

    Recommended Action: Generated revert patch forensics_revert_4aeefc40.patch and created hotfix branch forensics/hotfix-4aeefc40.

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

    About this skill

    Temporal Git Forensics — Causal Git Debugger & Virtual State Reconstructor

    Tired of AI agents getting lost in sprawling git commit histories, corrupting your active working tree with broken checkouts, or hallucinating the root cause of subtle production regressions?

    Temporal Git Forensics is a production-grade time-travel debugger and causal forensic engine for git repositories. It models commit history as a Directed Acyclic Graph (DAG) of state transitions, performs automated binary search bisects in isolated memory sandboxes, and reconstructs historical workspace snapshots without dirtying your working branch.

    ⚡ Key Capabilities:

    • Autonomous Causal Diagnosis: Evaluates recent commit graphs against error messages, stack traces, and symptom keywords to assign causal culpability scores (0–99%).
    • Automated In-Memory Bisect: Pinpoints breaking commits in logarithmic time by running unit tests or regex predicates in ephemeral snapshot directories—zero git lock contention.
    • Zero-Worktree State Reconstruction: Streams historical file trees and lockfiles into isolated folders (git archive | tar) without modifying HEAD, uncommitted edits, or stash queues.
    • Surgical Hotfix & Revert Generator: Computes inverted unified diff matrices and automatically provisions isolated hotfix branches (forensics/hotfix-<hash>).
    • Deep Blame & Provenance Graph: Traces line-level author attribution, code churn, and semantic commit categories ([BUGFIX], [BREAKING], [REVERT]).
    • Agent-Ready JSON Protocol: Native --json output designed for seamless integration with Claude Code, Cursor, Windsurf, and Antigravity swarms.

    📦 What's Included:

    • scripts/temporal_git_forensics.py (Zero-dependency CLI tool in Python standard library)
    • scripts/test_temporal_git_forensics.py (Automated unit & regression test suite with 100% pass rate)
    • scripts/demo_terminal_walkthrough.py (Animated terminal walkthrough simulation)
    • references/git_forensics_guide.md (CLI operator manual & incident post-mortem playbook)
    • references/causal_reasoning_spec.md (Formal mathematical specification of DAG culpability scoring)
    • Universal SKILL.md (< 40 lines Lean Core architecture)

    🔒 100% Local-First & Zero Telemetry

    Runs entirely on your local machine using standard git plumbing. No cloud egress, zero third-party dependencies.

    Requires local git binary access. Bisecting requires deterministic exit codes from test scripts. Snapshot reconstruction consumes disk space for each isolated state.

    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 any payment.

    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 1 month ago

    Requires

    Git

    Permissions

    Terminal / Shell
    Read Files
    Write Files
    Listed1 month ago

    What's inside

    Frequently Asked Questions

    This skill utilizes specialized protocols for DAG (Directed Acyclic Graph) traversal and automated bisecting, allowing it to perform deep forensic analysis without risking head-detachment errors or corrupting your active working directory.

    The skill is compatible with any test runner that provides standard exit codes (0 for success, non-zero for failure), including pytest, npm test, vitest, and custom bash scripts.

    Yes, the state reconstruction feature exports specific commit states to isolated sandbox directories, allowing you to inspect and test historical code without polluting your current working tree.

    Upon purchase, you receive the full skill protocol, including the forensic diagnosis engine, automated bisecting logic, and the structured JSON output schema for integration into your AI agent's workflow.

    The skill requires a local git repository and a deterministic test command; it cannot perform automated pinning if the failure is intermittent or if the git history is unreachable.

    New in Testing & Debugging