Netlify deploy: confirm the site before publishing

Use Netlify CLI to check auth, link the site, and select preview or production.

Skills

Proceed only when the user asks for Netlify hosting or deployment. Run `npx netlify status` first and confirm the signed-in user and site link. If unauthenticated, explain the browser OAuth flow through `npx netlify login`; never request `NETLIFY_AUTH_TOKEN`. Inspect the Git remote and `netlify.toml`, then verify build command and publish directory for the framework. Identify npm, yarn, or pnpm before installing dependencies. For an existing site, `npx netlify deploy` creates a preview by default. Use `npx netlify deploy --prod` only for a new site or an explicit production request. Site creation, account linking, and upload change external service state. Verify the deploy URL and logs; a local build is not proof of publication.

Permissions

Prerequisites

The user asks to deploy, host, or link a project to Netlify.
Requires a valid site project, Netlify CLI, and logged-in account; confirm the target site/team first.

Permissions

May authenticate, link or create a site, and upload build output through the CLI; production deployment changes an external site.
OAuth, dependency installation, and production publishing require user authorization; never expose tokens.

Limitations

Default to a draft deploy for an existing site; use `--prod` only for a new site or an explicit production request. Identify the package manager before installing dependencies.