VSCode

What This Skill Does

The VSCode skill is a specialized diagnostic and configuration assistant designed to eliminate common friction points when working with Visual Studio Code. It provides OpenClaw with deep knowledge of VSCode’s complex hierarchical settings, debug configuration patterns, and multi-root workspace behaviors. By interpreting current project structures and environment settings, the skill prevents silent failures—such as formatter conflicts, incorrect debugger path resolution, or terminal profile mismatches—before they derail your development workflow.

Installation

To integrate this skill into your OpenClaw agent, execute the following command in your terminal: clawhub install openclaw/skills/skills/ivangdavila/vscode

Use Cases

This skill is ideal for developers who frequently switch between different programming environments, work in polyglot workspaces, or manage complex debugging setups. It is particularly useful for troubleshooting issues where VSCode's behavior seems inconsistent, such as when project-level settings accidentally override global preferences, or when multiple formatter extensions clash on save. Use this skill to automate the setup of launch.json files for multi-process Node.js applications or to troubleshoot extension-host stability when VSCode starts crashing after updates.

Example Prompts

• "OpenClaw, my Prettier formatter isn't working on save, but ESLint is. Can you check my workspace settings for conflicts?"
• "I'm trying to debug a multi-process app. Can you generate a launch.json using a compound configuration?"
• "My TypeScript IntelliSense is completely unresponsive. Can you walk me through the steps to reset the language server and check for common configuration errors?"

Tips & Limitations

To maximize the utility of the VSCode skill, ensure that your workspace is in a trusted state, as restricted mode will disable the specific extensions and debugging capabilities you are trying to configure. Always remember that settings have a strict hierarchy: User > Workspace > Folder. If a setting isn't applying, check for an explicit override in your .vscode/settings.json file. Note that this skill acts as a configuration advisor; while it can provide diagnostic steps and code snippets, it does not physically modify your filesystem unless explicitly granted permission to write to .vscode configuration files. For issues with terminal variables, remember that VSCode terminals inherit the shell environment at the time of launch, not your standard login shell scripts like .bashrc. Restarting the terminal after environment changes is almost always required for the changes to manifest.