Commit changes

Commit changes in Visual Studio Code — with three ready prompts, from the immediate task to the lasting pattern.

3prompt heights
Open it in the interactive atlas →

3 ready prompts

Written for the moment this actually comes up.

Execute — do the immediate task

+
I finished the login fix and need to record it. Commit the staged changes with the message "FIX…
I finished the login fix and need to record it. Commit the staged changes with the message "FIX auth: prevent double-submit on login (issue #412)" and push to the current branch, ensuring the commit includes only the intended files and that the remote reflects the new SHA before I open the PR.

Improve — make it easier to accept

+
Before I commit this set of fixes, make the commit clear for reviewers: suggest a single-line…
Before I commit this set of fixes, make the commit clear for reviewers: suggest a single-line subject and a short body that explains the why, list any unrelated files accidentally staged, and flag changes that might require a migration or DB team notification so I can avoid surprise reviews.

Become — change the pattern

+
Over time my commits accumulate unrelated edits and generated files, making bisects and reviews…

Commits frequently mix unrelated changes

Over time my commits accumulate unrelated edits and generated files, making bisects and reviews painful. What three concrete practices and a brief pre-commit checklist should I adopt to keep commits focused, make git history meaningful for reviewers, and reduce time spent fixing bad commits later?

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.