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 me all stashes for this repository and include for each the stash name, short message, author,…
Execute — do the immediate task
+Show me all stashes for this repository and include for each the stash name, short message, author, date, and the files changed so I can tell which one to restore before today’s stand-up.
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 pick a stash to apply, make the list easy to scan: surface stashes sorted by date, show…
Improve — make it easier to accept
+Before I pick a stash to apply, make the list easy to scan: surface stashes sorted by date, show the first line of the stash message, list changed file paths and whether they include new, modified, deleted, or untracked files, and mark stashes that contain staged (index) state.
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 eight stashes with vague messages like WIP and quick-fix and I cannot tell which contains the…
Decide — diagnose the stuck moment
+I need a stash but there are eight with vague messages
I see eight stashes with vague messages like WIP and quick-fix and I cannot tell which contains the screen renderer change I started yesterday. I’m worried applying the wrong one will overwrite later work. Which stash attributes should I check to identify the correct one and what quick commands can I run to preview their contents safely?
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Become — change the pattern
+Every week developers create throwaway stashes with one-word messages and we waste time guessing…
Become — change the pattern
+stashes accumulate with inscrutable messages every week
Every week developers create throwaway stashes with one-word messages and we waste time guessing which is which. I want a team habit to reduce this friction. What naming convention and brief checklist should we require when creating a stash, and how can we enforce it with minimal overhead during interruptions?
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.