The four heights
The same task, four distances: today's deadline, the next reviewer, the stuck moment, the pattern.
Execute — do the immediate task
+Commit the staged changes with the message 'Auth token: add refresh flow, DB migration 20260714,…
Execute — do the immediate task
+Commit the staged changes with the message 'Auth token: add refresh flow, DB migration 20260714, tests added' and include a reference to issue tracker ticket JIRA-342. Check the commit message for a short summary line under 72 characters and that the body explains the migration and any manual steps. Then push to my feature branch and ping Marco for deployment planning.
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 commit, make the commit message approval-ready: produce a one-line summary under 72…
Improve — make it easier to accept
+Before I commit, make the commit message approval-ready: produce a one-line summary under 72 characters that emphasizes user impact, a short body listing the migration file and manual steps, and a JIRA-342 reference. Also flag any staged files that might need separate commits so the history remains reviewable.
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 ready to commit but the staged set contains debug logging changes I added while…
Decide — diagnose the stuck moment
+My staged changes include unrelated debug logs.
I’m ready to commit but the staged set contains debug logging changes I added while troubleshooting. Priya in QA will complain if these logs go to main and I can’t decide whether to keep them in this commit or split them out. What is the likely best practice here and the fastest practical way to proceed so I can push before Friday?
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Become — change the pattern
+Across multiple PRs we keep committing debug statements and formatting tweaks together with feature…
Become — change the pattern
+Our commits mix feature work with noisy debug changes repeatedly.
Across multiple PRs we keep committing debug statements and formatting tweaks together with feature changes, which makes review and blame noisy. What commit discipline (how to split commits, use of pre-commit hooks, review guidelines) will most quickly improve our history quality and reduce back-and-forth with Priya and reviewers?
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.