3 ready prompts
Written for the moment this actually comes up.
Improve — make it easier to accept
+Before I invite others to review, make the source-control view easier to scan: show unstaged…
Improve — make it easier to accept
+Before I invite others to review, make the source-control view easier to scan: show unstaged changes and untracked files at the very top, group changes by folder, and add a one-line diff preview for each file so a reviewer can spot big refactors without opening every file.
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 just pulled the latest branch, but the source-control pane shows no changes while I know I edited…
Decide — diagnose the stuck moment
+I opened the project and don’t see the changed files in the source-control pane
I just pulled the latest branch, but the source-control pane shows no changes while I know I edited three files. The team lead expects a review in two hours and I’m worried my local changes aren’t being detected or I’m on the wrong folder. Check whether the workspace root is the repo root, whether the git extension is active, and whether there are ignored patterns hiding files. If one of those, give the exact command or click path to fix it.
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Become — change the pattern
+Every sprint I lose time because I open the editor and start working without confirming the…
Become — change the pattern
+I keep missing staged changes when I open the project
Every sprint I lose time because I open the editor and start working without confirming the source-control view. I end up with forgotten staged files or accidental commits. Recommend a simple habit or checklist I can follow when opening a project that prevents missed changes and makes it routine to verify the working tree before coding.
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 editor work people do in Visual Studio Code.
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.