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 code and tests on Ahmed’s feature branch pass all CI checks and follow our lint rules. Approve…
Execute — do the immediate task
+The code and tests on Ahmed’s feature branch pass all CI checks and follow our lint rules. Approve the pull request and add a short comment calling out his refactor as useful for readability; remind him to squash the WIP commits before merge. Approve only if you confirm the database migration is reversible.
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 hit approve on the maintainer dashboard, make it easy for reviewers: summarize the change…
Improve — make it easier to accept
+Before I hit approve on the maintainer dashboard, make it easy for reviewers: summarize the change in one sentence, pull the migration file and state whether it is reversible, list any touched public APIs, and flag anything that would make a downstream integrator hesitate to accept this now. Include a one-line approval comment I can paste.
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
+Ahmed submitted a PR whose tests pass and lint is clean, but the migration file doesn’t clearly…
Decide — diagnose the stuck moment
+Tests passed but migration reversibility is unclear.
Ahmed submitted a PR whose tests pass and lint is clean, but the migration file doesn’t clearly indicate a down method. I’m the reviewer and don’t want to approve an irreversible migration by accident. Ahmed is reachable but busy. What’s the most likely explanation and the best next step I should take to resolve this without blocking him or the release?
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Become — change the pattern
+Over the past two months I’ve approved several PRs that later caused migration conflicts and…
Become — change the pattern
+I approve PRs that later cause schema issues.
Over the past two months I’ve approved several PRs that later caused migration conflicts and production rollbacks. I’m the team lead reviewing merges. Where am I losing credibility and time, and what single review habit should I adopt to prevent schema problems going forward?
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.