git-vet — Human review of AI-generated code.

Records when a human has built a mental model of an AI-generated change by attaching a Git-Vet trailer to the reviewed revision. The recorded commit hash identifies the exact revision that was inspected.

Example Usage

➤ git-vet

GIT VET   feature → main · primary branch

  1 awaiting review · 3 commits

  · 4063021  Add the update checker
  · 5eb4bcd  Wire the checker into the CLI
  › 1665311  Cache the last-checked timestamp  NEXT

NEXT UP

  git-vet show
  git-vet edit 1665311
  git-vet approve

➤ git-vet approve

NEXT  git-vet show to review 5eb4bcd.

Installation

Install from npm to get the CLI on your PATH:

npm install -g git-vet

Or run it ad-hoc with npx:

npx git-vet

Usage

A commit is approved once its message contains a trailer such as:

Git-Vet: gregtatum; commit=7a29c6f1

Every commit in the stack without that trailer counts as pending. The recorded hash documents the commit that was actually inspected; it's informational only, so rewriting history or garbage-collecting the original object doesn't invalidate the approval. Removing the trailer (git-vet reopen) requests another review.

The reviewer name is resolved in order:

1. git config vet.reviewer — an explicit override, e.g. your GitHub handle: git config vet.reviewer octocat
2. git config user.name
3. the local part of git config user.email

The review stack runs from an inferred base up to HEAD. The base is resolved in order:

1. an explicit --base <revision>
2. the branch's tracked upstream (@{upstream})
3. its configured push destination (@{push})
4. a uniquely-named remote branch matching the current branch name
5. a local main or master branch
6. a remote's default branch (origin/HEAD, preferred over other remotes)

If none of these resolve, pass --full to fall back to the full commit history from HEAD.

Command reference

See git-vet --help.