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 to restore a deleted helper file lib/helpers/formatDate.js that I accidentally removed and…
Execute — do the immediate task
+I need to restore a deleted helper file lib/helpers/formatDate.js that I accidentally removed and commit the recovery before the release cutoff. Give me the exact commands to recover it from the last commit where it existed, confirm its contents, and produce the commit message text I should use before pushing.
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 restore the deleted file, make the recovery audit-friendly: show how to find when it was…
Improve — make it easier to accept
+Before I restore the deleted file, make the recovery audit-friendly: show how to find when it was deleted and by whom, extract that revision of the file, and include a one-line explanation in the commit referencing the original deletion commit hash and why we’re restoring it. Show the exact commands and the note I should add to the PR description.
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 restored lib/helpers/formatDate.js from an older commit to get the build working, but some tests…
Decide — diagnose the stuck moment
+I reverted a deletion and now tests fail because the file version mismatches expectations
I restored lib/helpers/formatDate.js from an older commit to get the build working, but some tests now fail because behavior diverged. I don’t know whether to keep the old version, merge behaviors, or reimplement the new behavior. Recommend how to compare the deleted version to the last removed one, steps to produce a minimal reconciled file, and the pragmatic choice to make under a timebox for 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
+Our repo has several restores where someone pulled an old file back and it caused subtle bugs. Help…
Become — change the pattern
+We keep restoring deleted files that break assumptions later in QA
Our repo has several restores where someone pulled an old file back and it caused subtle bugs. Help me create a simple restore policy: how to check deletion context before recovery, when to open a ticket instead of restoring, and a short review checklist to follow when reintroducing removed code so QA isn’t surprised.
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.