3 ready prompts
Written for the moment this actually comes up.
Improve — make it easier to accept
+Before I send this for review, make the diff easy to scan for reviewers: surface the total number…
Improve — make it easier to accept
+Before I send this for review, make the diff easy to scan for reviewers: surface the total number of changed files and lines at the top, group changes by subsystem folder, mark renamed or moved files, and flag diffs that touch tests, CI config, or package version lines so reviewers don’t miss breaking changes.
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 pulled the latest branch and the local diff shows deletions in src/core I didn’t expect. The…
Decide — diagnose the stuck moment
+I opened the diff and there are unexpected deletions in src/core.
I pulled the latest branch and the local diff shows deletions in src/core I didn’t expect. The author is Sam on yesterday’s commit and I’m worried those deletes break the API. I can’t tell if Sam intended a refactor or an accidental overwrite. What’s the most likely cause and what’s the safest immediate action to take so I don’t ship a regression?
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 week a critical fix slips through because I skim huge diffs. I want one habit that reduces…
Become — change the pattern
+I keep missing important changes in large diffs.
Every week a critical fix slips through because I skim huge diffs. I want one habit that reduces that risk across repos: what review routine or diff-organization habit should I adopt to catch API and test-impacting changes without doubling my review time?
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.