VS Code Cheat Sheet

VS Code cheat sheet with real commands and snippets for setup, core workflows, debugging, and production-safe automation patterns. If you are working across tools, pair this with the Vim Cheat Sheet and Supabase Cheat Sheet.

Setup and Installation

Goal: Verify installation and CLI metadata

# Resolve command path from current shell
command -v code

# Print installed version to confirm runtime
code --version

# Read top-level help before using subcommands
code --help

Goal: Install or upgrade the tool on a workstation

# Install package with Homebrew on macOS
brew install visual-studio-code

# Upgrade to the latest available package
brew upgrade visual-studio-code

# Re-check version after upgrade
code --version

Goal: Run day-to-day commands

# Open current folder in VS Code
code .

# Open file at a specific line number
code -g src/index.ts:42

# Install extension from CLI
code --install-extension esbenp.prettier-vscode

# List currently installed extensions
code --list-extensions

Core Workflows

Goal: Capture command help for quick offline lookup

# Create docs folder for generated command references
mkdir -p docs/cli

# Write help output to a timestamped file
code --help > docs/cli/vscode-help.txt

# Search help output for a keyword
rg "config|auth|deploy" docs/cli/vscode-help.txt

Goal: Wrap repetitive commands in a script

# Create scripts directory for local automation
mkdir -p scripts

# Write repeatable health-check script
cat > scripts/check-vscode.sh <<'SH'
#!/usr/bin/env bash
set -euo pipefail
code --version
code --help >/dev/null
SH

# Make script executable and run it
chmod +x scripts/check-vscode.sh && ./scripts/check-vscode.sh

Configuration and Environment

Goal: Pin environment variables for predictable runs

# Define environment profile for local commands
export VSCODE_PROFILE=dev

# Persist profile in local shell configuration
echo 'export VSCODE_PROFILE=dev' >> ~/.zshrc

# Reload shell profile changes
source ~/.zshrc

Automation and CI

Goal: Add tool checks to CI pipeline

# Run lint/test/build in strict mode
set -euo pipefail

# Verify CLI exists before invoking workflow
command -v code

# Exit quickly if command is unavailable
code --version

Debugging and Troubleshooting

Goal: Collect diagnostics when commands fail

# Capture command output and exit code
code --help > /tmp/vscode-debug.log 2>&1; echo $?

# Inspect captured diagnostics
tail -n 80 /tmp/vscode-debug.log

# Check current shell PATH entries
echo $PATH | tr ':' '\n'

Common Gotchas

• Pin VS Code versions in CI so local and pipeline behavior match.
• Check tool authentication context before running write or deploy commands.
• Prefer non-interactive flags in scripts to avoid stalled jobs.
• Capture stderr logs in CI artifacts for faster incident triage.
• Keep secrets in environment variables, not committed scripts.

Related Sheets

• Vim Cheat Sheet — terminal editor navigation and editing speed.
• Supabase Cheat Sheet — daily Supabase commands and production-ready examples.
• Linux Cheat Sheet — filesystem, process, and service troubleshooting.