Netlify 部署技能：自动化 Web 项目部署到 Netlify 的完整指南

netlify-deploy by openai/skills

456 周安装量

15,300 GitHub Stars

GitHub

安装命令

npx skills add https://github.com/openai/skills --skill netlify-deploy

自动化云服务开发运维

🇨🇳中文介绍

Netlify 部署技能

使用 Netlify CLI 将 Web 项目部署到 Netlify，并智能检测项目配置和部署上下文。

概述

此技能通过以下方式自动化 Netlify 部署：

验证 Netlify CLI 身份验证
检测项目配置和框架
链接到现有站点或创建新站点
部署到生产或预览环境

前提条件

Netlify CLI：通过 npx 安装（无需全局安装）
身份验证：具有活动登录会话的 Netlify 账户
项目：当前目录中存在有效的 Web 项目
当沙盒环境阻止部署网络调用时，请使用 sandbox_permissions=require_escalated 重新运行。
部署可能需要几分钟时间。请使用适当的超时值。

身份验证模式

该技能使用预身份验证的 Netlify CLI 方法：

使用 npx netlify status 检查身份验证状态
如果未通过身份验证，则引导用户执行 npx netlify login
如果无法建立身份验证，则优雅地失败

身份验证使用以下任一方式：

基于浏览器的 OAuth（主要）：会打开浏览器进行身份验证

广告位招租

在这里展示您的产品或服务

触达数万 AI 开发者，精准高效

联系我们

1. 验证 Netlify CLI 身份验证

检查用户是否已登录 Netlify：

npx netlify status

预期输出模式：

✅ 已通过身份验证：显示已登录的用户电子邮件和站点链接状态
❌ 未通过身份验证：显示"Not logged into any site"或身份验证错误

如果未通过身份验证，引导用户：

这将打开一个浏览器窗口进行 OAuth 身份验证。等待用户完成登录，然后再次使用 netlify status 进行验证。

备选方案：API 密钥身份验证

如果浏览器身份验证不可用，用户可以设置：

export NETLIFY_AUTH_TOKEN=your_token_here

2. 检测站点链接状态

根据 netlify status 输出，确定：

已链接：站点已连接到 Netlify（显示站点名称/URL）
未链接：需要链接或创建站点

3. 链接到现有站点或创建新站点

如果已链接 → 跳转到步骤 4

如果未链接，尝试通过 Git 远程仓库链接：

# 检查项目是否基于 Git
git remote show origin

# 如果是基于 Git 的，提取远程 URL
# 格式：https://github.com/username/repo 或 git@github.com:username/repo.git

# 尝试通过 Git 远程仓库链接
npx netlify link --git-remote-url <REMOTE_URL>

如果链接失败（站点在 Netlify 上不存在）：

# 交互式创建新站点
npx netlify init

这将引导用户完成：

选择团队/账户
设置站点名称
配置构建设置
如果需要，创建 netlify.toml

在部署之前，确保项目依赖项已安装：

# 对于 npm 项目
npm install

# 对于其他包管理器，检测并使用适当的命令
# yarn install, pnpm install 等

5. 部署到 Netlify

根据上下文选择部署类型：

预览/草稿部署（现有站点的默认设置）：

npx netlify deploy

这将创建一个具有唯一 URL 的部署预览，用于测试。

生产部署（适用于新站点或明确的生产部署）：

npx netlify deploy --prod

这将部署到实时生产 URL。

CLI 检测构建设置（来自 netlify.toml 或提示用户）
在本地构建项目
将构建的资产上传到 Netlify
返回部署 URL

部署后，向用户报告：

部署 URL：此部署的唯一 URL
站点 URL：生产 URL（如果是生产部署）
部署日志：指向 Netlify 仪表板的日志链接
后续步骤：建议使用 netlify open 查看站点或仪表板

如果存在 netlify.toml 文件，CLI 会自动使用它。如果不存在，CLI 将提示输入：

构建命令：例如，npm run build、next build
发布目录：例如，dist、build、.next

常见框架默认值：

Next.js：构建命令 npm run build，发布目录 .next
React (Vite)：构建命令 npm run build，发布目录 dist
静态 HTML：无构建命令，发布当前目录

如果可能，该技能应从 package.json 检测框架并建议适当的设置。

完整工作流程示例

# 1. 检查身份验证
npx netlify status

# 如果未通过身份验证：
npx netlify login

# 2. 链接站点（如果需要）
# 首先尝试基于 Git 的链接
git remote show origin
npx netlify link --git-remote-url https://github.com/user/repo

# 如果站点不存在，则创建新站点：
npx netlify init

# 3. 安装依赖项
npm install

# 4. 部署（预览用于测试）
npx netlify deploy

# 5. 部署到生产环境（准备就绪时）
npx netlify deploy --prod

常见问题及解决方案：

"Not logged in" → 运行 npx netlify login

"No site linked" → 运行 npx netlify link 或 npx netlify init

"Build failed" → 检查 netlify.toml 或 CLI 提示中的构建命令和发布目录 → 验证依赖项是否已安装 → 查看构建日志以获取具体错误信息

"Publish directory not found" → 验证构建命令是否成功运行 → 检查发布目录路径是否正确

提升的网络访问权限

如果部署因网络问题（超时、DNS 错误、连接重置）而失败，请使用提升的权限重新运行部署（使用 sandbox_permissions=require_escalated）。当沙盒网络阻止出站请求时，部署需要提升的网络访问权限。

给用户的示例指导：

部署需要提升的网络访问权限才能部署到 Netlify。我可以使用提升的权限重新运行该命令——您希望我继续吗？

对于密钥和配置：

切勿将密钥提交到 Git
在 Netlify 仪表板中设置：站点设置 → 环境变量
在构建中通过 process.env.VARIABLE_NAME 访问

在生产部署之前，先使用 netlify deploy（不带 --prod）进行测试
运行 netlify open 在 Netlify 仪表板中查看站点
运行 netlify logs 查看函数日志（如果使用 Netlify Functions）
使用 netlify dev 进行本地开发（配合 Netlify Functions）

捆绑的参考（按需加载）

🇺🇸English

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:

Check authentication status with npx netlify status
If not authenticated, guide user through npx netlify login
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:

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:

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:

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:

# Check if project is Git-based
git remote show origin

# If Git-based, extract remote URL
# Format: https://github.com/username/repo or git@github.com:username/repo.git

# Try to link by Git remote
npx netlify link --git-remote-url <REMOTE_URL>

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

# Create new site interactively
npx netlify init

This guides user through:

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

4. Verify Dependencies

Before deploying, ensure project dependencies are installed:

# For npm projects
npm 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):

npx netlify deploy

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

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

npx netlify deploy --prod

This deploys to the live production URL.

Deployment process :

CLI detects build settings (from netlify.toml or prompts user)
Builds the project locally
Uploads built assets to Netlify
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

# 1. Check authentication
npx netlify status

# If not authenticated:
npx netlify login

# 2. Link site (if needed)
# Try Git-based linking first
git remote show origin
npx netlify link --git-remote-url https://github.com/user/repo

# If no site exists, create new one:
npx netlify init

# 3. Install dependencies
npm 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:

Never commit secrets to Git
Set in Netlify dashboard: Site Settings → Environment Variables
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

Netlify CLI Docs: https://docs.netlify.com/cli/get-started/
netlify.toml Reference: https://docs.netlify.com/configure-builds/file-based-configuration/

Bundled References (Load As Needed)

Weekly Installs

420

Repository

openai/skills

GitHub Stars

15.1K

First Seen

Feb 1, 2026

Security Audits

Gen Agent Trust HubWarn SocketPass SnykPass

Installed on

codex362

opencode357

gemini-cli347

github-copilot330

cursor325

kimi-cli321

Azure Data Explorer (Kusto) 查询技能：KQL数据分析、日志遥测与时间序列处理

100,500 周安装