Create a new branch — AI Prompts for Visual Studio Code

The four heights

The same task, four distances: today's deadline, the next reviewer, the stuck moment, the pattern.

Execute — do the immediate task

I need a feature branch for the payment module so QA can test without blocking main. Create branch…

I need a feature branch for the payment module so QA can test without blocking main. Create branch feature/payment-form from develop, push it to origin, and notify Priya on Slack. Confirm the branch exists on the remote and that my local HEAD is on it before I start coding.

Improve — make it easier to accept

Before I create the branch that will hold several WIP commits, make it review-friendly: suggest a…

Before I create the branch that will hold several WIP commits, make it review-friendly: suggest a concise branch name that shows the ticket number and scope, list any uncommitted changes that should be stashed or included, and warn about any outstanding merges from develop that would complicate the PR later.

Decide — diagnose the stuck moment

I attempted to create feature/payment-form from develop but git refused because I have uncommitted…

I tried to create the branch but git refused due to local changes

I attempted to create feature/payment-form from develop but git refused because I have uncommitted changes touching the same files. I can't tell if I should stash, commit, or amend the changes. Given that QA needs the new branch today and the changes are WIP, what is the safest immediate step to create the branch without losing work and keep history sane?

Become — change the pattern

I keep creating branches for small tasks and then getting blocked by lingering WIP changes, causing…

Creating branches repeatedly collides with unfinished work

I keep creating branches for small tasks and then getting blocked by lingering WIP changes, causing messy stashes and orphaned branches. Which three habits or a short checklist should I adopt at branch creation time to avoid conflicts, preserve work, and make PRs easy for reviewers like Priya?

Next to this one

Other code editor work people do in Visual Studio Code.

Change file encoding Close current editor Commit changes Configure tasks.json Create a launch configuration Create a new file Create a new folder Delete a file Disable an extension Edit settings JSON

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