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 a readable history for the last two weeks on branch release/2.3. Show the commit history…
Execute — do the immediate task
+I need a readable history for the last two weeks on branch release/2.3. Show the commit history from origin/release/2.3 including commit hashes, authors, dates, and one-line messages, limited to commits since 2026-07-01, and export it as a plain text summary I can paste into the release notes.
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 send the history to stakeholders, make the log easier to scan: highlight merge commits and…
Improve — make it easier to accept
+Before I send the history to stakeholders, make the log easier to scan: highlight merge commits and cherry-picks, surface commits that mention tickets HIGH- or SEC-, flag any commits by contractors Samir Patel or Megan Lee, and provide an executive-friendly two-line summary of the most important changes.
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 pulled origin/release/2.3 and now need to show what changed in modules/auth since 2.3.0. I’m not…
Decide — diagnose the stuck moment
+The QA lead asked for the commits touching the auth module since last release.
I pulled origin/release/2.3 and now need to show what changed in modules/auth since 2.3.0. I’m not sure how many merge commits or backports are included. What command sequence reliably gives a filtered commit history by path with author and date, and how do I tell if any entries were cherry-picked or backported?
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Become — change the pattern
+I regularly get requests for custom commit histories for releases and spend hours filtering logs.…
Become — change the pattern
+Stakeholders keep asking for ad-hoc commit histories for releases, taking my time.
I regularly get requests for custom commit histories for releases and spend hours filtering logs. Where am I losing time in my history workflow, and what templates, aliases, or release-note habits should I adopt so I can produce the same filtered history in under ten minutes?
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.