/git-diff

Make it your own.

In Claude Code, use the slash command and add your context. In Codex, select git-diff from the just-vibe skill picker, then send the same brief.

Version 0.11.0 also supports /jv git-diff, /just-vibe git-diff and /jv:git-diff in Claude. See shortcut setup and context examples.

What the agent does

1. Resolve the requested comparison and its refs, separating index versus HEAD, worktree versus index and branch versus merge-base.
2. Inspect rename, binary and submodule metadata and read surrounding context, then group hunks by purpose and identify unrelated edits.

Inputs

• working/index state or exact base/head refs and desired review focus.

Optional context: scope, references, constraints, successCriteria, environment, mode, budget.

Scope

Reads

Selected changes and their behavioral meaning; no staging or editing.

Writes

No source changes in inspect/plan. Save only requested planning artifacts. A separately requested repair uses the relevant implementation workflow.

Mode

Inspect; working/index state or exact base/head refs and desired review focus.

Prerequisites

Git, exact repository/worktree, and readable refs/index. Record branch, HEAD, staged/unstaged/untracked state before mutation. Preserve unrelated edits and never default to broad staging, hard reset, clean, force push, or history rewriting.

Expected output

• Comparison refs, files and hunks grouped by purpose, impacted contracts, notable risks, unrelated changes and files requiring deeper review.

How the work is checked

• Staged and unstaged changes are not conflated; a binary change is acknowledged without invented contents.

When to stop or clarify

• Missing comparison refs require resolution. Do not assume every change belongs to the current task.

Handling missing context

Infer

Read repository root, HEAD, branch, refs and staged/unstaged/untracked distinctions; use the configured human identity.

Assume

Limit an ambiguous inspection to the current repository and report that scope; preserve all existing changes.

Ask

Before mutation, resolve uncertain commit membership, destination ref or history-rewrite intent; do not ask again about already authorized exact actions.

Technical guidance

Evidence

Resolve comparison refs and merge-base, then inspect rename, mode, binary and submodule changes as well as text.

Method

Summarize user-visible behavior and dependencies between hunks; identify which tree each diff represents.

Pitfall

Branch-tip comparison and merge-base comparison answer different questions; text-only review misses executable-bit changes.

Check

Cite a representative hunk for each behavior claim and account for changed files outside ordinary source extensions.

Situational decisions

When rename, binary or submodule entries appear: Report their metadata and scope instead of inventing text diffs or flattening submodule changes.

The coding agent follows this workflow using its available tools. Installation does not grant service access or guarantee an outcome. Read the compatibility notes.

Keep exploring