Netlify Deploy

openai/skills/skills/.curated/netlify-deploy

作者 openai49f948faa925無授權條款28K 個星標收錄於 2026年11月20日更新於 2026年11月20日儲存庫3 週前更新

Deploy web projects to Netlify using the Netlify CLI (`npx netlify`). Use when the user asks to deploy, host, publish, or link a site/repo on Netlify, including preview and production deploys.

精選僅含說明DevOps 與雲端
AI 產生的概覽

指導使用 Netlify CLI 將網站專案部署到 Netlify,涵蓋驗證、站台連結以及預覽或正式部署。

功能
引導代理透過 npx netlify 將網站專案部署到 Netlify:檢查驗證狀態、偵測框架與建置設定、連結既有站台或建立新站台、安裝相依套件,並執行預覽或正式部署。也涵蓋 netlify.toml 的處理、常見錯誤排除,以及回報部署網址與站台網址。此技能僅提供指示,產出為已部署的站台及其網址與日誌。
適用情境
當使用者要求在 Netlify 上部署、代管、發佈或連結站台或程式碼儲存庫時使用,包含預覽部署與正式部署。
執行需求
透過 npx 執行 Netlify CLI(不需全域安裝)、已透過瀏覽器 OAuth 或 NETLIFY_AUTH_TOKEN 環境變數完成驗證的 Netlify 帳號、目前目錄中有效的網站專案,以及供部署呼叫使用的外網連線(可能需要提高權限)。不附帶指令碼。

Netlify Deployment Skill

Deploy web projects to Netlify using the Netlify CLI with intelligent detection of project configuration and deployment context.

Overview

This skill automates Netlify deployments by:

  • Verifying Netlify CLI authentication
  • Detecting project configuration and framework
  • Linking to existing sites or creating new ones
  • Deploying to production or preview environments

Prerequisites

  • Netlify CLI: Installed via npx (no global install required)
  • Authentication: Netlify account with active login session
  • Project: Valid web project in current directory
  • When sandboxing blocks the deployment network calls, rerun with sandbox_permissions=require_escalated.
  • The deployment might take a few minutes. Use appropriate timeout values.

Authentication Pattern

The skill uses the pre-authenticated Netlify CLI approach:

  1. Check authentication status with npx netlify status
  2. If not authenticated, guide user through npx netlify login
  3. Fail gracefully if authentication cannot be established

Authentication uses either:

  • Browser-based OAuth (primary): netlify login opens browser for authentication
  • API Key (alternative): Set NETLIFY_AUTH_TOKEN environment variable

Workflow

1. Verify Netlify CLI Authentication

Check if the user is logged into Netlify:

bash
npx netlify status

Expected output patterns:

  • ✅ Authenticated: Shows logged-in user email and site link status
  • ❌ Not authenticated: "Not logged into any site" or authentication error

If not authenticated, guide the user:

bash
npx netlify login

This opens a browser window for OAuth authentication. Wait for user to complete login, then verify with netlify status again.

Alternative: API Key authentication

If browser authentication isn't available, users can set:

bash
export NETLIFY_AUTH_TOKEN=your_token_here

Tokens can be generated at: https://app.netlify.com/user/applications#personal-access-tokens

2. Detect Site Link Status

From netlify status output, determine:

  • Linked: Site already connected to Netlify (shows site name/URL)
  • Not linked: Need to link or create site

3. Link to Existing Site or Create New

If already linked → Skip to step 4

If not linked, attempt to link by Git remote:

bash
# Check if project is Git-basedgit remote show origin
# If Git-based, extract remote URL# Format: https://github.com/username/repo or [email protected]:username/repo.git
# Try to link by Git remotenpx netlify link --git-remote-url <REMOTE_URL>

If link fails (site doesn't exist on Netlify):

bash
# Create new site interactivelynpx netlify init

This guides user through:

  1. Choosing team/account
  2. Setting site name
  3. Configuring build settings
  4. Creating netlify.toml if needed

4. Verify Dependencies

Before deploying, ensure project dependencies are installed:

bash
# For npm projectsnpm install
# For other package managers, detect and use appropriate command# yarn install, pnpm install, etc.

5. Deploy to Netlify

Choose deployment type based on context:

Preview/Draft Deploy (default for existing sites):

bash
npx netlify deploy

This creates a deploy preview with a unique URL for testing.

Production Deploy (for new sites or explicit production deployments):

bash
npx netlify deploy --prod

This deploys to the live production URL.

Deployment process:

  1. CLI detects build settings (from netlify.toml or prompts user)
  2. Builds the project locally
  3. Uploads built assets to Netlify
  4. Returns deployment URL

6. Report Results

After deployment, report to user:

  • Deploy URL: Unique URL for this deployment
  • Site URL: Production URL (if production deploy)
  • Deploy logs: Link to Netlify dashboard for logs
  • Next steps: Suggest netlify open to view site or dashboard

Handling netlify.toml

If a netlify.toml file exists, the CLI uses it automatically. If not, the CLI will prompt for:

  • Build command: e.g., npm run build, next build
  • Publish directory: e.g., dist, build, .next

Common framework defaults:

  • Next.js: build command npm run build, publish .next
  • React (Vite): build command npm run build, publish dist
  • Static HTML: no build command, publish current directory

The skill should detect framework from package.json if possible and suggest appropriate settings.

Example Full Workflow

bash
# 1. Check authenticationnpx netlify status
# If not authenticated:npx netlify login
# 2. Link site (if needed)# Try Git-based linking firstgit remote show originnpx netlify link --git-remote-url https://github.com/user/repo
# If no site exists, create new one:npx netlify init
# 3. Install dependenciesnpm install
# 4. Deploy (preview for testing)npx netlify deploy
# 5. Deploy to production (when ready)npx netlify deploy --prod

Error Handling

Common issues and solutions:

"Not logged in" → Run npx netlify login

"No site linked" → Run npx netlify link or npx netlify init

"Build failed" → Check build command and publish directory in netlify.toml or CLI prompts → Verify dependencies are installed → Review build logs for specific errors

"Publish directory not found" → Verify build command ran successfully → Check publish directory path is correct

Troubleshooting

Escalated Network Access

If deployment fails due to network issues (timeouts, DNS errors, connection resets), rerun the deploy with escalated permissions (use sandbox_permissions=require_escalated). The deploy requires escalated network access when sandbox networking blocks outbound requests.

Example guidance to the user:

The deploy needs escalated network access to deploy to Netlify. I can rerun the command with escalated permissions—want me to proceed?

Environment Variables

For secrets and configuration:

  1. Never commit secrets to Git
  2. Set in Netlify dashboard: Site Settings → Environment Variables
  3. Access in builds via process.env.VARIABLE_NAME

Tips

  • Use netlify deploy (no --prod) first to test before production
  • Run netlify open to view site in Netlify dashboard
  • Run netlify logs to view function logs (if using Netlify Functions)
  • Use netlify dev for local development with Netlify Functions

Reference

Bundled References (Load As Needed)

  • CLI commands [blocked]
  • Deployment patterns [blocked]
  • netlify.toml guide [blocked]

來源與署名

來源:openai/skills位於skills/.curated/netlify-deploy提交49f948f

授權條款: 無授權條款

內容歸原作者所有。SourceWeft 從公開儲存庫中收錄這些內容。

在 README 中新增徽章

向讀者展示該技能已收錄於 SourceWeft,徽章連結到本頁。

「Listed on SourceWeft」徽章預覽
[![Listed on SourceWeft](https://sourceweft.com/badge/skills/gh-openai-skills-netlify-deploy.svg)](https://sourceweft.com/skills/gh-openai-skills-netlify-deploy?utm_source=readme&utm_medium=badge)

檢舉或申請下架