The four heights
The same task, four distances: today's deadline, the next reviewer, the stuck moment, the pattern.
Execute — do the immediate task
+The feature branch is four commits ahead of main and conflicts in two files. Rebase the branch onto…
Execute — do the immediate task
+The feature branch is four commits ahead of main and conflicts in two files. Rebase the branch onto main, resolve the conflicts in the test helpers and README, run the full test suite locally, and push the rebased commits, keeping the original author and commit messages intact.
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 rebase this feature branch onto main, make it easy to finish cleanly: show which files…
Improve — make it easier to accept
+Before I rebase this feature branch onto main, make it easy to finish cleanly: show which files will conflict, provide suggested conflict resolutions for the test helper and CI config, list the exact git commands to perform the rebase while preserving author metadata, and remind me which checks to run locally before pushing.
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 started rebasing Jordan’s branch onto main and hit conflicts in the CI config and a shared test…
Decide — diagnose the stuck moment
+Rebase produced conflicts I’m not sure how to resolve.
I started rebasing Jordan’s branch onto main and hit conflicts in the CI config and a shared test helper. Jordan expects to keep his tests but isn’t available to weigh in. I’m worried resolving this wrong will change test behavior or break CI. What likely caused these conflicts and what is the best next move to resolve them safely without Jordan?
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 spends a lot of time rebasing feature branches because main moves fast and many PRs touch…
Become — change the pattern
+Branches repeatedly need rebases and conflict resolution.
Our team spends a lot of time rebasing feature branches because main moves fast and many PRs touch shared test helpers and CI configs. I coordinate merges. Where are we losing time and momentum, and which single change to our branching or review process would reduce frequent rebases and conflicts?
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 code hosting work people do in GitHub.
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.