3 ready prompts
Written for the moment this actually comes up.
Execute — do the immediate task
+I need these three files removed from version control and the repo left in a clean state:…
Execute — do the immediate task
+I need these three files removed from version control and the repo left in a clean state: build/output.log, .cache/local.db, and tmp/debug.txt. Remove them from tracking but keep the files on disk, commit the change with a clear message, and verify nothing else is unintentionally staged. Sign the commit with my name and use Friday as the commit date if the system supports it.
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 remove files from tracking, make it easy for reviewers to accept the change. Show the…
Improve — make it easier to accept
+Before I remove files from tracking, make it easy for reviewers to accept the change. Show the exact diff that will be committed after removal, surface any other files that will be staged by accident, and call out whether removing these tracked files will affect CI or deployment scripts. If any tracked copies are still referenced by build steps, highlight those lines and suggest the minimal code change.
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 several projects we repeatedly add generated files to the repo and later have to remove…
Become — change the pattern
+We keep having to untrack generated files across many repos.
Across several projects we repeatedly add generated files to the repo and later have to remove them. This wastes time on churn and causes accidental commits and large repos. Where is the recurring failure and what single habit or small checklist change would stop this from happening?
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.