Skip to main content

Git Diff Mode

Git Diff Mode packages changed files and surrounding context for sponsor fixes, pull request reviews, and audit follow-ups where the patch matters as much as the full file.

Download for macOSBuy Pro

Why it matters

  • Review questions often depend on what changed between two refs, not only current file contents.
  • Sponsor fixes and audit follow-ups need a clear before/after review surface.
  • PR review prompts are stronger when the diff and relevant full files are bundled together intentionally.

How it works

  • Select base and head refs, a commit range, staged changes, unstaged changes, or another supported comparison mode.
  • Choose diff-only output when the patch is enough.
  • Choose diff plus full files when the model needs the changed code in surrounding file context.
  • Include Git metadata so branch, commit, and dirty-tree state are visible in the bundle.

Example workflow

  1. Open a Git repository.
  2. Choose a base/head comparison for the sponsor fix or PR.
  3. Select diff-only or diff plus full file contents.
  4. Add related unchanged files when the patch depends on shared types or helpers.
  5. Run the secret scanner and export a review bundle.

Example diff context summary

Base ref: main
Head ref: sponsor/auth-fix
Comparison mode: refs
Include mode: diff + full file contents
Changed files:
  src/billing/pricing.ts
  src/auth/session.ts
Selected supporting files:
  src/auth/types.ts
  tests/pricing.test.ts

Limitations

  • Git Diff Mode is a review aid and does not replace manual patch review.
  • Uncommitted work should be reviewed carefully so staged, unstaged, and untracked state is understood.
  • Git metadata is read-only in PastePrompt; use Git tooling for branch and commit operations.

Build a repeatable context workflow.

Download the macOS app, review the docs, and contact support for Founder or Pro licensing during launch.

Download for macOSView pricing