Wisegit

Created By
Sandip1242 months ago
MCP server that extracts decision intent from git history and protects intentional code from AI modification.
Overview

WiseGit is a local MCP server that reconstructs the "why" behind code decisions from git history — so AI agents respect what was intentional, not just what compiles.

The problem: LLMs treat all code equally. A manually-tested race condition fix (sleep(350)) and a broken stub look identical — both are just text. When Claude Code sees "find bugs," it removes the sleep. Production incident. The proof of intention exists in git history, but nobody extracts it.

What wisegit does:

  1. Indexes your git history — walks every commit, parses diffs at the AST level using Tree-sitter (C#, TypeScript, JavaScript, Python, Go, Rust), classifies commits (STRUCTURED/DESCRIPTIVE/NOISE), and extracts decision intent.

  2. Computes freeze scores — each function gets a 0–1 score derived from 7 signal categories: git history (reverts, age, contributor count), issue enrichment (Won't Fix/By Design from GitHub/GitLab), code structure (magic numbers, defensive patterns), test signals, structural importance (PageRank from call graph), Naur theory signals (institutional knowledge loss), and Aranda signals (timeline gaps, forgotten patterns).

  3. Serves decision manifests via MCP — before any file edit, the AI agent calls get_file_decisions and sees which functions are FROZEN (don't touch without override), STABLE (proceed with caution), or OPEN (safe to modify). Theory holders show who on the team understands each function.

  4. Enables seamless overrides — when the AI needs to modify frozen code, it calls create_override with a reason. The user approves with one click in Claude Code. The override is recorded in an append-only audit trail shared with the team via git.

8 MCP tools:

  • get_file_decisions — decision manifest with freeze scores, theory holders, override status
  • get_freeze_score — detailed score breakdown for a function
  • get_function_history — full chronological decision timeline
  • get_theory_gaps — functions with no active theory holders (Naur death)
  • get_branch_context — branch merge history and migration context
  • search_decisions — keyword search across all past decisions
  • create_override — override frozen functions (user approves in UI)
  • extract_intent — extract intent for NOISE commits using host LLM via MCP sampling

Key features:

  • Zero config — npx @sandip124/wisegit setup in any repo, that's it
  • SQLite database (no Docker, no PostgreSQL, no external services)
  • Team support via .wisegit/ directory tracked by git (JSONL files merge cleanly)
  • AI-era commit origin detection (HUMAN / AI_REVIEWED / AI_UNREVIEWED)
  • Theory holder tracking per function (healthy / fragile / critical risk levels)
  • HTML codebase health report (wisegit report)
  • Grounded in 12 published software engineering papers

Academic foundation: Naur (1985) theory building, Aranda & Venolia (2009) bug repository analysis, Kim et al. (2007) fault prediction from cached history, Ying et al. (2004) co-change mining, Giger et al. (2011) AST-level change analysis, Aryani et al. (2014) domain-based coupling, and 6 more.

Server Config

{
  "mcpServers": {
    "wisegit": {
      "command": "npx",
      "args": [
        "-y",
        "@sandip124/wisegit",
        "serve"
      ]
    }
  }
}
Project Info
Created At
2 months ago
Updated At
2 months ago
Author Name
Sandip124
Star
-
Language
-
License
-
Category

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

20 hours ago
Gpt Scrambler

2 days ago