Netlify Deploy

Handles the full Netlify deployment flow through their CLI, from checking authentication status to pushing sites live. It walks through linking existing sites or spinning up new ones, detects your framework from package.json when possible, and defaults to preview deploys so you can test before going to production. The authentication pattern is sensible: checks if you're logged in, prompts for browser OAuth if not, falls back to API tokens. One thing to appreciate is how it handles the netlify.toml detection and prompts for build settings when the config is missing. Useful when you want to deploy without leaving your editor or need to automate Netlify pushes from an AI workflow.

skills.sh installs: 3.7K
GitHub stars: 51
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add netlify/context-and-tools --skill netlify-deploy --agent claude-code

Installs into .claude/skills of the current project.

Files

Netlify deploy

Modern CLI

netlify deploy              # manual draft deploy (no CI)
netlify deploy --prod       # deploy straight to production
netlify create              # new project from a natural-language prompt
netlify deploy --allow-anonymous   # temp project, claim within 1 hour
npm update -g netlify-cli   # skew protection needs 23.11.0+

A deploy is a versioned, atomic snapshot: Netlify uploads only changed files and switches the live site only after all files land — the site is never in an inconsistent state. A deploy can be a preview or a production version served at your primary domain.

Continuous deployment vs manual deploys: Deploy with Git and the Netlify CLI support continuous deployment — a push auto-triggers a build. Drag and drop and the API create one-off manual deploys. Manual deploys (netlify deploy) do not run a build command; drag-and-drop while logged in is the only exception (framework auto-detected).

⚠ When linking or creating a site, add .netlify to .gitignore. Every linking path writes .netlify/state.json, which must not be committed.