Guide for using the Netlify CLI and deploying sites. Use when installing the CLI, linking sites, deploying (Git-based or manual), managing environment variables, or running local development. Covers netlify dev, netlify deploy, Git vs non-Git workflows, and environment variable management.
93
89%
Does it follow best practices?
Impact
100%
1.12xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
npm install -g netlify-cli # Global (for local dev)
npm install netlify-cli -D # Local (for CI)Requires Node.js 18.14.0+.
netlify login # Opens browser for OAuth
netlify status # Check auth + linked site statusFor CI, set NETLIFY_AUTH_TOKEN environment variable instead.
Check if already linked with netlify status. If not:
# Interactive
netlify link
# By Git remote (if using Git)
netlify link --git-remote-url https://github.com/org/repo
# Create new site
netlify init # With Git CI/CD setup
netlify init --manual # Without Git CI/CDSite ID is stored in .netlify/state.json. Add .netlify to .gitignore.
Set up with netlify init. Automatic deploys trigger on push/PR:
Build runs on Netlify's servers. Configure build settings in netlify.toml.
Build locally, then upload:
netlify deploy # Draft deploy (preview URL)
netlify deploy --prod # Production deploy
netlify deploy --dir=dist # Specify output directoryThis works without Git — useful for prototypes, local-only projects, or CI pipelines.
netlify devWraps your framework's dev server and provides:
For projects using Vite (React SPA, TanStack Start, SvelteKit, Remix), the Vite plugin provides Netlify platform primitives directly in the framework's dev server:
npm install @netlify/vite-plugin// vite.config.ts
import netlify from "@netlify/vite-plugin";
export default defineConfig({ plugins: [netlify()] });Then run your normal dev command (npm run dev) — no netlify dev wrapper needed. This gives you access to Blobs, DB, Functions, and environment variables during development.
See the netlify-frameworks skill for framework-specific local dev guidance.
# Set
netlify env:set API_KEY "value"
netlify env:set API_KEY "value" --secret # Hidden from logs
netlify env:set API_KEY "value" --context production # Context-specific
# Get
netlify env:get API_KEY
# List
netlify env:list
netlify env:list --plain > .env # Export to file
# Import from file
netlify env:import .env
# Delete
netlify env:unset API_KEYVariables can be scoped to deploy contexts:
netlify env:set API_URL "https://api.prod.com" --context production
netlify env:set API_URL "https://api.staging.com" --context deploy-preview
netlify env:set DEBUG "true" --context branch:feature-xNetlify.env.get("VAR") (preferred) or process.env.VARVITE_-prefixed vars via import.meta.env.VITE_VARPUBLIC_-prefixed vars via import.meta.env.PUBLIC_VARNever use VITE_ or PUBLIC_ prefix for secrets — these are exposed to the browser.
| Command | Description |
|---|---|
netlify status | Auth and site link status |
netlify dev | Start local dev server |
netlify build | Run build locally (mimics Netlify environment) |
netlify deploy | Draft deploy |
netlify deploy --prod | Production deploy |
netlify dev:exec <cmd> | Run command with Netlify environment loaded |
netlify env:list | List environment variables |
netlify clone org/repo | Clone, link, and set up in one step |
cffaf74
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.