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 remote branch origin/feature/refactor-login from the shared repo — verify there are no…
Execute — do the immediate task
+Remove the remote branch origin/feature/refactor-login from the shared repo — verify there are no open pull requests pointing to it and inform the release manager before final deletion; fail if the branch contains commits not merged into main or release/1.2.
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 remote-branch deletion so reviewers won't be surprised: show any open PRs or pipeline…
Improve — make it easier to accept
+Prepare the remote-branch deletion so reviewers won't be surprised: show any open PRs or pipeline references, list commits unique to origin/feature/refactor-login and where else they appear, and draft a one-line message to post in the team's channel explaining why we're deleting it.
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 scheduled removal of origin/feature/refactor-login and a teammate just said a pull request might…
Decide — diagnose the stuck moment
+I scheduled deletion and someone said a PR still points at it
I scheduled removal of origin/feature/refactor-login and a teammate just said a pull request might still reference it. I don't know if that PR is merged, closed, or draft, and I can't reach the author before the cleanup window ends. How do I quickly determine whether deleting the remote branch will break the PR or CI, and what's the safest next move if the status is ambiguous?
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 remote keeps accumulating branches and people delete them without announcement, breaking CI and…
Become — change the pattern
+Remotes get cluttered with old branches and surprise deletions
Our remote keeps accumulating branches and people delete them without announcement, breaking CI and confusing reviewers. I need a small team practice to reduce clutter without blocking work. What policy and simple gating steps should we adopt for remote-branch deletion, and how do we make sure owners and CI consumers get notified reliably?
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.