deps-install

created	"2025-12-16T00:00:00.000Z"
modified	"2026-08-07T00:00:00.000Z"
reviewed	"2026-08-07T00:00:00.000Z"
allowed-tools	Bash, Read, Write
model	sonnet
args	[package-names] [--dev] [--global]
argument-hint	[package-names] [--dev] [--global]
description	Deps install: auto-detect package manager (uv, bun, npm, yarn, pnpm, cargo, go) and run the right install. Use when installing deps or syncing lockfiles.
name	deps-install

When to Use This Skill

Use this skill when...	Use justfile-expert instead when...
Installing packages without picking a manager up front	Defining a project-local just install recipe
One-off --global or --dev installs across mixed projects	Standardising just deps / just sync for a team
Auto-detecting between uv, bun, npm, cargo, and go	The repo already exposes installation as a recipe

Use this skill when...	Use shell-expert instead when...
The user just wants the install command run	Writing a custom installer script with retries or branching
Syncing the lockfile via the right native subcommand	Composing multi-package-manager bootstrap logic in shell

Context

• Package files: !find . -maxdepth 1 \( -name "package.json" -o -name "pyproject.toml" -o -name "requirements.txt" -o -name "Cargo.toml" -o -name "go.mod" -o -name "Gemfile" \) -type f
• Lock files: !find . -maxdepth 1 \( -name "uv.lock" -o -name "package-lock.json" -o -name "yarn.lock" -o -name "pnpm-lock.yaml" -o -name "Cargo.lock" -o -name "go.sum" \) -type f

Parameters

Parse $ARGUMENTS and bind these before running anything. They are supplied by the caller; nothing substitutes them for you.

Token in $ARGUMENTS	Binds	Default when absent
Non-flag tokens	PACKAGES — space-separated package names	empty → install everything from the manifest
--dev	DEV — add to development dependencies	off
--global	GLOBAL — install globally rather than into the project	off

Every command below is written with a literal PACKAGES placeholder — substitute the bound value when you run it.

Execution