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 the commit history for the auth-service for the past month. Show all commits on main from…
Execute — do the immediate task
+I need the commit history for the auth-service for the past month. Show all commits on main from 2026-06-01 to 2026-07-01, include author, date, short message, and the files each commit touched. Export that as a plain text list so I can paste it 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 commit history to QA, make it easy to scan: pull the commits on main since…
Improve — make it easier to accept
+Before I send the commit history to QA, make it easy to scan: pull the commits on main since 2026-06-01, group them by feature (login, token refresh, rate limit), highlight commits that changed public APIs or migrations, and flag any commits without accompanying PRs or that lack test 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
+QA says token expiry behavior changed last week but I can’t identify which commit caused it. I have…
Decide — diagnose the stuck moment
+QA just asked why a behavior changed but I can’t find the responsible commit
QA says token expiry behavior changed last week but I can’t identify which commit caused it. I have the date range and the auth-service repo. What’s the quickest way to pinpoint the commit that altered token expiry, what grep or blame steps should I run, and who on the team is the best person to ask if commit messages are sparse?
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Become — change the pattern
+We spend hours tracing behavioral changes because commits are poorly labeled and PRs are…
Become — change the pattern
+We lose time hunting for changes across noisy commit histories
We spend hours tracing behavioral changes because commits are poorly labeled and PRs are inconsistent. Which three habits will most reduce investigation time across repositories — for example, standardized commit prefixes, mandatory PR checklists, or automated changelog generation — and which one habit will give the biggest immediate payoff for our small team?
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 code hosting work people do in GitHub.
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.