VS Code Workflow Cheat Sheet

topMost Useful VS Code Shortcuts#

Ten shortcuts that cover the majority of daily VS Code tasks. If you learn nothing else, learn these.

#VS Code Workflow Shortcuts by Task#

Find the right shortcut or command based on what you want to accomplish, not by category name.

~Editing Shortcuts#

Line manipulation, multi-cursor, formatting, and comments. These shortcuts save the most keystrokes per day. See also: indent multiple lines, format code, autoformat.

Line operations

Multi-cursor editing

Formatting and comments

@Navigation Shortcuts#

Move between files, symbols, and positions without the mouse.

Command Palette prefix syntax (interactive)

Click a row to see how the input changes. Type a prefix character to switch the Palette into a different mode.

/Search and Replace Shortcuts#

From quick in-file finds to project-wide regex replacements. See also: full find-and-replace guide.

Common search patterns (enable regex mode first)

>_Integrated Terminal Workflow#

VS Code's integrated terminal runs shell commands without leaving the editor. You can open multiple terminals, switch shell profiles (PowerShell, Bash, Zsh, WSL, and others), and run build tasks directly. The terminal opens in the workspace root by default. See the full VS Code terminal guide.

Run a Node project

npm install
npm run dev

Run a Python file

python file.py

Create and activate a virtual environment

python -m venv .venv
.venv\Scripts\activate

python3 -m venv .venv
source .venv/bin/activate

pyPython Workflow#

VS Code has strong Python support via the Python extension. Interpreter selection, venv management, and debugging are all available without leaving the editor. Rows marked with * use the Command Palette or panel rather than a direct keyboard shortcut.

Recommended Python project setup

python -m venv .venv
.venv\Scripts\activate
pip install -r requirements.txt

python3 -m venv .venv
source .venv/bin/activate
pip install -r requirements.txt

gitGit Workflow in VS Code#

VS Code's Source Control view handles most Git tasks visually. Rows marked with * use the panel, not a keyboard shortcut. For full terminal Git use the integrated terminal.

Command Palette Git commands Adv

F5Debugging Shortcuts#

VS Code's built-in debugger works with most languages through extensions. Press F5 to start. For simple files you usually do not need a launch.json.

Basic debugging flow

1. 1Open the file you want to debug.
2. 2Add a breakpoint with F9. A red dot appears in the gutter.
3. 3Press F5 to start the debugger.
4. 4When execution pauses, inspect variables in the Run and Debug panel.
5. 5Use F10 (step over) or F11 (step into) to move through the code.
6. 6Press F5 to continue or ShiftF5 to stop.

When do you need launch.json?

runTasks Workflow#

Tasks let you run shell commands (build, test, lint, start server) from VS Code without opening a terminal each time. Tasks are defined in .vscode/tasks.json.

Common task commands

Example tasks.json Adv

{
  "version": "2.0.0",
  "tasks": [
    {
      "label": "Run dev server",
      "type": "shell",
      "command": "npm run dev",
      "group": "build",
      "problemMatcher": []
    },
    {
      "label": "Run Python tests",
      "type": "shell",
      "command": "python -m pytest",
      "problemMatcher": []
    }
  ]
}

{}How to Customise VS Code Shortcuts#

Every VS Code shortcut can be changed, removed, or added. Use the Keyboard Shortcuts editor for a visual interface or edit keybindings.json directly for full control. See also: VS Code settings guide, open settings.json.

Open the Keyboard Shortcuts editor

The three keybinding fields

Example: add a custom shortcut

[
  {
    "key": "ctrl+alt+t",
    "command": "workbench.action.terminal.toggleTerminal"
  }
]

Example: conditional keybinding Adv

[
  {
    "key": "ctrl+shift+r",
    "command": "workbench.action.reloadWindow",
    "when": "editorTextFocus"
  }
]

?!Troubleshooting VS Code Shortcuts#

If a shortcut is not working, the most common causes are conflicts with extensions, the OS, or a previous custom keybinding.

Shortcut does not fire

Find shortcut conflicts

1. 1Open the Keyboard Shortcuts editor (CtrlK CtrlSCmdK CmdS).
2. 2Search for the key combination, e.g. CtrlD.
3. 3Right-click any result and choose Show Same Keybindings.
4. 4Unbind or reassign any conflicts.

Terminal shortcuts behave differently

The integrated terminal captures focus differently from the editor. Some key combinations are sent directly to the shell rather than VS Code. If a shortcut works in the editor but not the terminal, customise it with a when: terminalFocus clause in keybindings.json. See the VS Code terminal guide for focus and shell-configuration tips, and how to enable error squiggles for related diagnostic steps.

QVS Code Shortcuts FAQ#

refRelated Guides#

All internal links in one place, organised by topic cluster.