# Netlify Deploy

> Use when the user wants to deploy, publish, preview, or link a web project on Netlify; prefer the Netlify CLI, verify auth and site linkage first, and default to preview deploys unless production is explicitly requested.

- Skill: `hebertzhu/netlify-deploy` (Agent Skill)
- Install (CLI): `npx skillmds@latest add hebertzhu/netlify-deploy`
- Raw SKILL.md: https://api.skillmd.com/api/skills/hebertzhu/netlify-deploy/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: DevOps & Infra
- Author: hebertzhu (https://skillmd.com/u/hebertzhu)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/hebertzhu/netlify-deploy

---


# Netlify Deploy

## Intent
- Use for Netlify site linking, preview deploys, production deploys, and `netlify.toml`-aware deployment setup.

## Default operating pattern
1. Check `npx netlify status` first to confirm CLI access, login state, and whether the current repo is already linked.
2. If the repo is not linked, inspect the Git remote before choosing between `npx netlify link --git-remote-url <remote>` and `npx netlify init`.
3. Inspect `package.json`, `netlify.toml`, and the detected package manager before installing dependencies or guessing build settings.
4. Default to `npx netlify deploy` for a preview URL; only use `npx netlify deploy --prod` when the user explicitly asks for production.
5. Return the deploy URL, the site URL if available, and any remaining manual steps such as setting environment variables in the Netlify dashboard.

## Pack fit
- Included in: `deploy-ops`
- Keep instructions CLI-first, host-agnostic, and reusable across modern web projects.

## Boundary
- Do not claim the deploy succeeded unless the CLI returns a success result or URL.
- Do not invent build commands, publish directories, or site settings when the project config is ambiguous.