Create and apply a patch

Create and apply a patch in Git — with three ready prompts, from the immediate task to the lasting pattern.

3prompt heights
Open it in the interactive atlas →

3 ready prompts

Written for the moment this actually comes up.

Execute — do the immediate task

+
I have staged changes I want to share as a patch file. Create a patch from HEAD~1..HEAD and save it…
I have staged changes I want to share as a patch file. Create a patch from HEAD~1..HEAD and save it as fix-auth.patch in the repo root, then show the command to apply that patch in another clone and verify it applies cleanly without committing.

Improve — make it easier to accept

+
Before I send this patch to the security reviewer, make it easy to apply and inspect: produce an…
Before I send this patch to the security reviewer, make it easy to apply and inspect: produce an email-friendly patch file showing author, date, and exact diff, add a short header summarizing the functional change and risk, and list the apply command and a fallback if the patch fails due to context lines.

Become — change the pattern

+
I often create patches that colleagues cannot apply because their trees have diverged. Where am I…

I keep sending patches that don't apply cleanly across forks

I often create patches that colleagues cannot apply because their trees have diverged. Where am I losing time and trust, and what habitual change (how I create patches, what base I use, or a brief pre-send checklist) would make my patches reliably apply across forks and save rounds of back-and-forth?

Next to this one

Other version control work people do in Git.

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.
Copyright © LLOS.ai · 2026 — original pedagogy, voice, and design — all rights reserved.

The rest of the map

Same library, five ways in.