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 the file src/config/settings.yml from branch release/2.4 restored into my current branch…
Execute — do the immediate task
+I need the file src/config/settings.yml from branch release/2.4 restored into my current branch hotfix/2.4.1 so I can patch a config value. Replace the working copy in my hotfix branch with that file, preserving file history where possible, and stage it for commit. Confirm the file diff before I commit.
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 this change from another branch, make it easy for Raj to accept: show the exact…
Improve — make it easier to accept
+Before I commit this change from another branch, make it easy for Raj to accept: show the exact lines changed between our current hotfix/2.4.1 version and release/2.4's src/config/settings.yml, call out any nearby configuration keys he might object to, and note if the file had been renamed or moved recently that could confuse a reviewer.
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 checked out src/config/settings.yml from release/2.4 into hotfix/2.4.1 to fix an environment…
Decide — diagnose the stuck moment
+I pulled a file from release/2.4 but now I’m not sure why tests fail
I checked out src/config/settings.yml from release/2.4 into hotfix/2.4.1 to fix an environment flag, and now unit tests fail. I’m afraid the file brought in unrelated changes or a different indentation style I can’t spot. I don’t know what exact differences were introduced or whether I preserved line endings. How can I quickly compare the file I pulled to the previous hotfix version, revert just the parts that break tests if needed, and document the change for Raj?
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 several fixes I keep importing whole files from other branches to save time, and reviewers…
Become — change the pattern
+I habitually pull full files from other branches without checking context
Over several fixes I keep importing whole files from other branches to save time, and reviewers keep flagging hidden changes that break tests or behavior. I want a new approach that reduces review churn and accidental regressions: what smaller-granularity habit should I adopt when borrowing code from another branch, and a practical pre-commit checklist to catch context-sensitive issues before a reviewer sees them?
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.