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 check the repo status before I push. Show uncommitted changes, untracked files, current…
Execute — do the immediate task
+I need to check the repo status before I push. Show uncommitted changes, untracked files, current branch name, and whether my local branch is ahead, behind, or diverged from origin/main. If there are conflicts staged, report them and stop so I can resolve before pushing.
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 run the status check, make it easy to act on: surface which files are uncommitted and…
Improve — make it easier to accept
+Before I run the status check, make it easy to act on: surface which files are uncommitted and which are untracked, highlight anything that would be accidentally included in a commit, show if hooks will run, and flag if my branch differs from origin/main in ways that will trigger a force-push or conflict.
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 see local changes but I don't know if I accidentally left debug logs or local config. I'm afraid…
Decide — diagnose the stuck moment
+I'm about to push but I'm not sure what changed locally.
I see local changes but I don't know if I accidentally left debug logs or local config. I'm afraid pushing will break CI or expose secrets. What exact checks should I run now to know it's safe to push, and what immediate fixes should I apply if I find risky files or divergence from the remote?
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Become — change the pattern
+Team members frequently push with messy working trees: leftover debug prints, accidental local…
Become — change the pattern
+Developers often push without checking the working tree.
Team members frequently push with messy working trees: leftover debug prints, accidental local configs, and half-done files, causing flaky CI and rollbacks. What simple workflow or pre-push habit will eliminate most of these incidents, and how should I introduce it so busy engineers adopt it quickly?
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.