Stage/unstage files — AI Prompts for Visual Studio Code

3 ready prompts

Written for the moment this actually comes up.

Execute — do the immediate task

I need to prepare a clean commit for review. Stage src/auth.ts and src/session.ts and ensure dist/…

I need to prepare a clean commit for review. Stage src/auth.ts and src/session.ts and ensure dist/ and node_modules/ are unstaged. If any other files are staged, unstage them, then show me the staged file list so I can run the final tests before committing.

Improve — make it easier to accept

Before I stage files for the PR, make it easy for the reviewer: highlight which files must be…

Before I stage files for the PR, make it easy for the reviewer: highlight which files must be staged for the story, call out generated files that should never be staged, and point out files that commonly sneak into the index so I can confirm the exact diff before committing.

Become — change the pattern

I repeatedly stage generated files and unrelated artifacts, which causes rework and noisy commits.…

I keep staging generated or irrelevant files

I repeatedly stage generated files and unrelated artifacts, which causes rework and noisy commits. Which three small changes to my workflow, .gitignore, or staging routine will prevent these mistakes and make staging a deliberate, low-friction step for reviewers and CI?

Next to this one

Other code editor work people do in Visual Studio Code.

Search and open symbol Select column/block Set a breakpoint Show references Split editor view Step through debugger Switch editor tabs Toggle minimap Toggle side bar Toggle word wrap

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.

The rest of the map

Same library, five ways in.

Work Atlasthe whole map, interactive Careers1,949 jobs and their real tasks Soft skillsthe human part of the work Activities500 things people do Prompt Librarybrowse every prompt