Back to Directory/Developer Tools

GitWhy — The Context Layer for Git

The shared AI context engine for git — save, search, and share the reasoning behind code changes.

Developer Toolsv0.7.9
View on GitHub

GitWhy Agent Skills

Agent skills for GitWhy — save the reasoning, decisions, and trade-offs behind AI-generated code.

Install

npx skills add gitwhy-cli/gitwhy

Or install for a specific agent:

npx skills add gitwhy-cli/gitwhy --agent claude
npx skills add gitwhy-cli/gitwhy --agent cursor
npx skills add gitwhy-cli/gitwhy --agent codex

What's Included

gitwhy skill

Teaches your AI coding agent to save, retrieve, and search structured context linked to git commits. Works via MCP tools or CLI commands.

Trigger phrases:

  • "Save this session with GitWhy"
  • "What context do we have on authentication?"
  • "Show me the context tree"
  • "Post the context to the PR"

Prerequisites

Install the GitWhy CLI first:

curl -fsSL https://gitwhy.dev/install.sh | sh

Or via Homebrew:

brew install gitwhy-cli/tap/git-why

Then run setup:

git why setup

Links

Installation

Source-derived launch command. Check the maintainer’s required arguments and credentials before running:

bash
npx -y gitwhy-mcp

Set up in your AI client

Merge this template into ~/Library/Application Support/Claude/claude_desktop_config.json. Keep existing servers. Add any arguments, credentials, and permissions required by the maintainer; this template has not been install-tested.

json
{
  "mcpServers": {
    "io-github-gitwhy-cli-gitwhy": {
      "command": "npx",
      "args": [
        "-y",
        "gitwhy-mcp"
      ]
    }
  }
}

Restart Claude Desktop completely for changes to take effect. Confirm the server appears connected in the client’s tool list, then try a read-only example from its documentation.

Claude Desktop setup reference

Package

gitwhy-mcpnpm

Compatible MCP Clients

GitWhy — The Context Layer for Git works with any MCP-compatible client. Copy the config snippet from the Configuration section above and add it to the file shown for your client, then restart the application.

  • Claude Desktop~/Library/Application Support/Claude/claude_desktop_config.jsonRestart Claude Desktop completely for changes to take effect.
  • Cursor~/.cursor/mcp.jsonRestart Cursor for changes to take effect.
  • VS Code.vscode/mcp.jsonReload VS Code window for changes to take effect.
  • Windsurf~/.codeium/windsurf/mcp_config.jsonRestart Windsurf for changes to take effect.
  • Claude Code.mcp.jsonSave at the project root, then start Claude Code in that project and review the MCP server approval prompt. Keep real credentials out of shared files.

Learn More

Webflow MCP Server: Connect Claude Code and Review CMS AccessUse the current /mcp endpoint and inspect a known collection first. Learn when the Designer Bridge App is needed and how to review agent changes.Read articleOpenCode MCP Server Setup: Add Any MCP to Your TerminalOpenCode doesn't lock you into one AI provider, and it doesn't lock you into one MCP transport either. This guide covers the real opencode.json config, the exact JSON keys for local and remote servers, and which MCPFind-listed servers actually make sense in a terminal workflow.Read articleGitHub vs GitLab MCP: Connections and AccessUse the server for the platform holding your work. Compare account access and a real repository task before expanding permissions or changing hosts.Read article