Quickstart

Step 0 — Install the CLI

Prerequisite: You need the git-why CLI installed before continuing. Install it here →

Step 1 — Set up GitWhy

Run the setup wizard:

git why setup

You’ll see a multi-select menu:

  GitWhy — Context Layer for Git

  How should your coding agent connect with GitWhy?
  (Select at least one. You can combine multiple options.)

  [x] MCP Server (Recommended)
      → Agent gets 8 tools: save, list, search, get, status, sync, publish, post PR

  [x] Skill Files (Recommended)
      → Creates .claude/skills/gitwhy/ with format guidance

  [ ] Rules (CLAUDE.md / AGENTS.md)
      → Adds GitWhy instructions to your project rule file

  [ ] Hook
      → Injects GitWhy instructions on every prompt

  ──────────────────────────────────────────────
  Repo-local capture setup runs automatically on your first save.

Select MCP + Skill files for Claude Code, Cursor, and most MCP-capable agents. Use arrow keys to move, Space to toggle, Enter to confirm.

Step 2 — Work and commit

Work on a feature with your coding agent and make a few commits.

Step 3 — Save the session

When you’re done, tell your agent:

Save this session with GitWhy.

The agent generates a structured context, then saves it:

Context saved: ctx_a1b2c3d4

That first save also prepares .git/gitwhy/ and installs the post-commit hook for future commits in the repository.

Step 4 — Browse locally

git why log

ctx_a1b2c3d4  JWT implementation setup  authentication/jwt-implementation  2m ago

git why get ctx_a1b2c3d4   # Read the full context
git why tree               # Browse by domain and topic

Your context is saved locally. Share it with your team in two ways:

Post to PR
Sync to Dashboard

Post a structured context comment on your GitHub pull request:

git why post-pr [context-id...]

Reviewers see the reasoning behind your changes directly on the PR.See the PR Comments guide and CLI reference for full options.

Sync contexts to your team’s cloud dashboard:

git why push <context-id>

Browse all shared contexts by repo, domain, and topic.See the Team Sync guide and CLI reference for full options.

Getting Started

Core Features

Sharing & Collaboration

Interfaces

Integration Guide

CLI Reference

Context Format

Plans & Pricing

Step 0 — Install the CLI

Step 1 — Set up GitWhy

Step 2 — Work and commit

Step 3 — Save the session

Step 4 — Browse locally

What’s next

Context format

CLI reference

​Step 0 — Install the CLI

​Step 1 — Set up GitWhy

​Step 2 — Work and commit

​Step 3 — Save the session

​Step 4 — Browse locally

​Step 5 — Share with your team

​What’s next

Context format

CLI reference

Step 0 — Install the CLI

Step 1 — Set up GitWhy

Step 2 — Work and commit

Step 3 — Save the session

Step 4 — Browse locally

Step 5 — Share with your team

What’s next