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 full list of all branches in this repository — show local and remote branches with their…
Execute — do the immediate task
+I need a full list of all branches in this repository — show local and remote branches with their last commit date and author, so I can decide what to keep and what to prune before the release tomorrow.
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
+Prepare the branch list for the release lead: put active release branches and hotfixes at the top,…
Improve — make it easier to accept
+Prepare the branch list for the release lead: put active release branches and hotfixes at the top, flag branches not updated in 60 days, and include the remote tracking name and last commit summary so it's easy to authorize deletions.
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 listed branches and found ten with similar names like feature/auth-v1 and feature/auth-v1-2; I'm…
Decide — diagnose the stuck moment
+I asked for branches and got more than I expected
I listed branches and found ten with similar names like feature/auth-v1 and feature/auth-v1-2; I'm not sure which one the QA team is testing. I can't ask them now without interrupting testing. What's the most reliable way to determine which branch is the tested one and which are leftover drafts, using commit history and remote tracking info, so I can clean up without deleting the branch under test?
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 sprint we end up with duplicate or abandoned branches and our branch list turns into noise,…
Become — change the pattern
+Too many near-duplicate branches accumulate every sprint
Every sprint we end up with duplicate or abandoned branches and our branch list turns into noise, costing engineering time and PR confusion. What practical habits and a lightweight cleanup cadence should we put in place so branches are meaningful, reviewers can find the right branch, and deletions don't surprise anyone?
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.