Set a breakpoint — AI Prompts for Visual Studio Code

2 ready prompts

Written for the moment this actually comes up.

Execute — do the immediate task

Set a breakpoint on the current line in the file I'm editing so the next debug session will pause…

Set a breakpoint on the current line in the file I'm editing so the next debug session will pause there. Add the breakpoint even if the file is unsaved and mark it as active; if the file is not part of any launch config, still set the UI marker and show whether the breakpoint is bound. Ladder L1

Improve — make it easier to accept

Before I add a breakpoint, surface issues that would make it pointless: warn if the file is…

Before I add a breakpoint, surface issues that would make it pointless: warn if the file is generated, if source maps don't match, or if the running process uses a different build. If valid, suggest conditional or logpoint options and a quick note to explain why I placed the breakpoint for future me. Ladder L2

Next to this one

Other code editor work people do in Visual Studio Code.

Run linting on file Save current file Search across files Search and open symbol Select column/block Show references Split editor view Stage/unstage files Step through debugger Switch editor tabs

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