# gitwhy

> Use this tool when you need to capture and share the reasoning behind code changes, or search for the context behind specific commits. Gitwhy solves the problem of lost knowledge and context switching by providing a shared AI context engine for git, allowing coding agents to understand the "why" behind every commit. It takes in commit messages and PR updates as inputs and outputs searchable, shareable explanations for coding decisions.

Canonical page: https://skillsregistry.net/skills/gitwhy-cli-gitwhy  
JSON: https://api.skillsregistry.net/v1/skills/gitwhy-cli-gitwhy

## Description

The shared AI context engine for git — save, search, and share the reasoning behind code changes. Captures the why behind every commit and slide on PRs for coding agents.

## Trust

- **Trust score (0–1):** 0.50
- **Verification tier:** unverified

## Facts

- **Version:** 1.0.0
- **Skill type:** atomic
- **Execution layer:** mcp-remote
- **Runtime environment:** api
- **Category:** version-control
- **Updated:** 2026-05-12

## Source

- **Source listing:** [Smithery](https://smithery.ai/server/gitwhy-cli/gitwhy)

## Use it

Resolve this record through the SkillsRegistry MCP server (no auth, read-only):

```
claude mcp add --transport http --scope user skillsregistry https://api.skillsregistry.net/mcp
```

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "get_skill",
    "arguments": {
      "slug": "gitwhy-cli-gitwhy"
    }
  }
}
```

REST: `GET https://api.skillsregistry.net/v1/skills/gitwhy-cli-gitwhy` · pull for local use: `GET https://api.skillsregistry.net/v1/skills/gitwhy-cli-gitwhy/pull`

---
SkillsRegistry indexes agent skills from public registries and GitHub. Skills we have analysed are scanned with Circle-IR and scored on six dimensions; each listing states its scan coverage. More: https://skillsregistry.net/llms.txt