Skip to main content
git why setup presents a multi-select menu for choosing integration methods. At least one must be selected. You can use multiple methods together — for example, MCP for tool access and Skill files for format guidance.

​
Supported agents

GitWhy supports 34 coding agents. git why setup auto-detects installed agents and configures the supported integration methods. See the full supported agents list for details on each agent, including config paths and MCP format support. Claude Code also supports Hook integration for per-prompt injection.

​
Skill file paths by agent

​
Methods at a glance

MCP + Skill files is the recommended default for all agents.
  • MCP gives the agent eight tools (gitwhy_save, gitwhy_get, gitwhy_search, gitwhy_list, gitwhy_status, gitwhy_sync, gitwhy_publish, gitwhy_post_pr) to call GitWhy.
  • Skill files give the agent the knowledge — the context format template, when to save, and how to structure good output.
Together: the agent knows what to do (from skill files) and how to do it (from MCP tools).

​
Repo-local setup

git why setup is global. On the first git why save in a repository, GitWhy completes repo-local setup:
  • prepares .git/gitwhy/ local storage
  • copies repo-scoped credentials when available
  • configures notes.rewriteRef
  • installs .git/hooks/post-commit to run git-why hook-run
This hook is infrastructure, not an integration method. It tracks future commits in that repository so the ## Commits section is easier to populate on later saves.

​
Choose your method

MCP Server

Gives the agent eight tools for saving, browsing, searching, and sharing context. Works with all 34 supported agents.

Skill files

Creates skill files with format guidance the agent discovers automatically.

Rules

Appends GitWhy instructions to your project rule file. Universal fallback.

Hook

Injects instructions on every prompt. Guarantees awareness at higher token cost.