The four heights
The same task, four distances: today's deadline, the next reviewer, the stuck moment, the pattern.
Execute — do the immediate task
+Show the diff between feature/auth-redesign and main focusing on src/auth, tests that changed, and…
Execute — do the immediate task
+Show the diff between feature/auth-redesign and main focusing on src/auth, tests that changed, and the package manifest. Summarize functional impacts and list any potential merge conflicts so I can prepare the PR and brief Jo before tomorrow’s merge window.
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Improve — make it easier to accept
+Before I open the PR, make the branch comparison reviewer-friendly: surface high-level changes,…
Improve — make it easier to accept
+Before I open the PR, make the branch comparison reviewer-friendly: surface high-level changes, group file-level diffs by subsystem, highlight lines that change public interfaces and package versions, and flag any added files that look like credentials or large binaries.
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Decide — diagnose the stuck moment
+I have feature/auth-redesign passing locally, but I’m not certain which changes on main will break…
Decide — diagnose the stuck moment
+I ran a local build on feature/auth-redesign but tests pass differently on main
I have feature/auth-redesign passing locally, but I’m not certain which changes on main will break it. I’m worried about subtle API changes and dependency bumps. Which files and commits should I inspect first to diagnose likely breakage and what’s the fastest way to run a comparison that shows those risk areas?
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Become — change the pattern
+Over multiple merges we repeatedly hit last-minute conflicts and missed dependency bumps that break…
Become — change the pattern
+merge conflicts and overlooked dependency changes keep delaying our releases
Over multiple merges we repeatedly hit last-minute conflicts and missed dependency bumps that break CI. I want one habit to reduce these disruptions. What workflow change should our team adopt—branching strategy, pre-merge checks, or developer responsibility—to catch these problems earlier with minimal extra overhead?
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
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.