skills/nvm-skills/nvm-shell-integration/SKILL.md
Configure automatic nvm version switching when changing directories, using shell hooks for bash, zsh, and fish. Covers auto-use on cd, PATH restoration, and nvm deactivate. Use when the user wants automatic Node version switching per project, nvm use to run on directory change, or needs to deactivate nvm and restore system PATH.
npx skillsauth add partme-ai/full-stack-skills nvm-shell-integrationInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Add automatic nvm use on directory changes so the correct Node version activates per project.
Add auto-switching for bash (append to ~/.bashrc):
cdnvm() {
command cd "$@" || return $?
nvm_path="$(nvm_find_up .nvmrc | command tr -d '\n')"
if [ -n "$nvm_path" ]; then
local nvm_node_version=$(nvm version "$(cat "$nvm_path/.nvmrc")")
if [ "$nvm_node_version" = "N/A" ]; then
nvm install
elif [ "$nvm_node_version" != "$(nvm version)" ]; then
nvm use
fi
fi
}
alias cd='cdnvm'
Deactivate nvm and restore PATH when needed:
nvm deactivate # Removes nvm from PATH, restores system node
nvm use system # Switch to system-installed Node
Verify auto-switching works:
echo "20" > /tmp/test-project/.nvmrc
cd /tmp/test-project # Should auto-switch to Node 20
node -v # Should show v20.x.x
Note: Base shell loading belongs to nvm-setup. This skill adds deeper integration on top.
examples/shell-integration.md - Overview of integration optionsexamples/auto-use-bash.md - Bash auto-switching hookexamples/auto-use-zsh.md - Zsh auto-switching hookexamples/auto-use-fish.md - Fish auto-switching hookexamples/restore-path.md - PATH restoration and nvm deactivateshell integration, auto use, PATH restore, nvm deactivate, auto switch, cdnvm
development
Provides per-component and per-API examples with cross-platform compatibility details for uni-app, covering built-in components, uni-ui components, and APIs (network, storage, device, UI, navigation, media). Use when the user needs official uni-app components or APIs, wants per-component examples with doc links, or needs platform compatibility checks.
tools
Creates new uni-app projects via the official CLI or HBuilderX with Vue 2/Vue 3 template selection, manifest.json and pages.json configuration, and directory structure setup. Use when the user wants to scaffold a new uni-app project, initialize project files with a single command, or set up the development environment.
tools
Browses, installs, configures, and manages plugins from the uni-app plugin market (ext.dcloud.net.cn) including component plugins, API plugins, and template plugins with dependency handling. Use when the user needs to find and install uni-app plugins, configure plugin settings, manage plugin dependencies, or integrate third-party components.
tools
Develops native Android and iOS plugins for uni-app including module creation, JavaScript-to-native communication, and plugin packaging for distribution. Use when the user needs to build custom native modules, extend uni-app with native capabilities (camera, Bluetooth, sensors), or create publishable native plugins.