The four heights
The same task, four distances: today's deadline, the next reviewer, the stuck moment, the pattern.
Execute — do the immediate task
+Remove the obsolete stash labelled WIP from last month and then clear any stashes older than 90…
Execute — do the immediate task
+Remove the obsolete stash labelled WIP from last month and then clear any stashes older than 90 days. Confirm which stashes were deleted and log who created them and when before you remove anything others might need.
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 deleting stashes, surface the risk: show each stash’s creation date, author, changed files,…
Improve — make it easier to accept
+Before deleting stashes, surface the risk: show each stash’s creation date, author, changed files, and whether it diverges from any current branch. Flag stashes that probably contain unique work or were authored by teammates so I can avoid deleting theirs by mistake.
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’m cleaning up the repo’s stashes and found one authored by Priya that looks useful. The policy is…
Decide — diagnose the stuck moment
+I found a stash with someone else’s name and a useful change but I was told to clear old stashes
I’m cleaning up the repo’s stashes and found one authored by Priya that looks useful. The policy is to clear stashes older than 90 days, but I don’t know if Priya still needs it. Should I delete it, message Priya first, or archive its patch elsewhere? What’s the least risky option that keeps the history usable?
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Become — change the pattern
+Our team periodically clears stashes en masse and later discovers useful work was lost. I want a…
Become — change the pattern
+we repeatedly lose time recovering accidentally deleted stashes
Our team periodically clears stashes en masse and later discovers useful work was lost. I want a single new habit that prevents accidental deletion but keeps the stash list manageable. Recommend a retention and review workflow and one practical safeguard we can adopt today to avoid losing teammates’ work.
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.