Show changes between commits — AI Prompts for Git

The four heights

The same task, four distances: today's deadline, the next reviewer, the stuck moment, the pattern.

Execute — do the immediate task

I need to confirm what changed between commit 9f3c2b and 2a7e1d on branch hotfix/payment. Show a…

I need to confirm what changed between commit 9f3c2b and 2a7e1d on branch hotfix/payment. Show a unified diff of code and a file-level summary of added, removed, and modified files, and save the diff to diffs/payment-hotfix-9f3c2b-2a7e1d.patch.

Improve — make it easier to accept

Before I send this diff to the payment engineer, make it easy to assess risk: produce a per-file…

Before I send this diff to the payment engineer, make it easy to assess risk: produce a per-file summary with function-level hunks, flag any changes to public APIs or DB schema, show which tests cover altered files, and annotate lines that remove error handling or change auth checks.

Decide — diagnose the stuck moment

On hotfix/payment I have commits 9f3c2b (before) and 2a7e1d (after). I’m worried the regression…

A customer reported a regression after a hotfix; I need to see what changed between two commits.

On hotfix/payment I have commits 9f3c2b (before) and 2a7e1d (after). I’m worried the regression came from an underestimated change. What’s the fastest way to get a clear, file-by-file diff that highlights behavioral changes and potential API or security impacts so I can point the engineer to the suspicious hunks?

Become — change the pattern

I spend too much time debugging regressions because I run diffs in panic and miss the risky…

I keep chasing regressions because diffs are hard to interpret under pressure.

I spend too much time debugging regressions because I run diffs in panic and miss the risky changes. What reproducible habit or small tooling setup can I adopt so diffs between commits surface likely causes quickly (API changes, removed checks, schema edits) and I can triage regressions in under twenty minutes?

Next to this one

Other version control work people do in Git.

Restore a deleted file Rewrite commit history Run hooks manually Set up hooks Show branch graph Sign commits or tags Split a commit into multiple Squash commits during rebase Squash multiple commits Stage changed files

Every task here came from the work, not from a feature list — which is why the prompts name what you want done and never the button that does it. The tool changes; the work does not.

The rest of the map

Same library, five ways in.

Work Atlasthe whole map, interactive Careers1,949 jobs and their real tasks Soft skillsthe human part of the work Activities500 things people do Prompt Librarybrowse every prompt