skills.rest
costrict-plugins-repo
costrict-plugins-repoOFFICIAL
Explore all skills by this author →
GitHub

netlify-deploy

Create and manage Netlify deploys via Git continuous deployment, CLI, and netlify.toml contexts.

Updated May 19, 2026
Search Tags:#ci/cd#deployment#netlify#continuous deployment#netlify-cli#netlify.toml#deploy previews
One-click install
npx skills add https://github.com/costrict-plugins-repo/anthropic-netlify-skills --skill netlify-deploy-costrict-plugins-repo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: netlify-deploy
Source: https://github.com/costrict-plugins-repo/anthropic-netlify-skills/tree/main/codex/skills/netlify-deploy
Command: npx skills add https://github.com/costrict-plugins-repo/anthropic-netlify-skills --skill netlify-deploy-costrict-plugins-repo

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Deploying to Netlify involves many paths — Git continuous deployment, manual CLI uploads, drag-and-drop, Deploy to Netlify buttons — each with its own configuration rules, footguns, and failure modes. This Skill gives an AI agent the exact, current facts needed to link repos, run deploys, configure per-context build settings, and diagnose failed deploys without searching documentation. ## Core Features & Use Cases - Git continuous deployment and previews: Connect a repo, configure production branches, Deploy Previews, branch deploys, and skip-deploy tokens like [skip ci]. - CLI and manual deploys: Run netlify deploy, --prod, and anonymous deploys, with warnings about .netlify/state.json in .gitignore and manual --prod deploys being replaced by the next Git push. - Deploy configuration and troubleshooting: Write per-context netlify.toml build settings, set up build hooks and Deploy to Netlify buttons, enable skew protection, and fix failed or secrets-flagged deploys. - Use Case: A developer pushes code and the deploy fails secrets scanning. The agent explains that a real leaked secret must be rotated, or a false positive scoped narrowly with SECRETS_SCAN_OMIT_KEYS, and that the previously published deploy is still live so there is nothing to roll back. ## Quick Start Ask the agent to link this repository to a Netlify site and create a production deploy using the Netlify CLI.

Frequently Asked Questions about netlify-deploy

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I deploy a site to Netlify from the CLI?▼

Run netlify deploy for a draft preview deploy or netlify deploy --prod to publish to production. Link the directory first with netlify link or netlify init, and note that manual deploys do not run a build command unless you upload prebuilt output with --dir.

How do I set up continuous deployment on Netlify?▼

Connect your Git repository via netlify init or the Netlify UI, and Netlify builds and deploys on every push. Pushes to the production branch trigger production deploys, pull requests get Deploy Previews, and branch deploys must be enabled separately in build settings.

Why did my Netlify deploy fail secrets scanning?▼

Secrets scanning fails a deploy when a value resembling a credential appears in published output. If it is a real secret, rotate it and stop shipping it; for false positives, scope exclusions narrowly with SECRETS_SCAN_OMIT_KEYS or SECRETS_SCAN_OMIT_PATHS rather than disabling the scanner.

Can I roll back a Netlify deploy to a previous version?▼

A failed deploy never publishes, so the previous deploy stays live and there is nothing to restore. For a bad published deploy, the recommended path is to fix forward: revert the offending commit and let CI redeploy.

How do I configure different build settings per deploy context in netlify.toml?▼

Use [context.production], [context.deploy-preview], [context.branch-deploy], or a branch name as a context key, each with its own command and environment block. More specific contexts override general ones, and file-based config overrides UI settings.

Does a manual netlify deploy --prod persist on a Git-connected site?▼

No. The next push to the production branch silently replaces a hand-shipped manual deploy. If the manual deploy must stay live, lock the published deploy in the Netlify UI before pushing again.

Related Skills

Explore More Software Engineering Skills→
WhaleylawWhaleylaw

netlify-deployment-specialist

Configure Netlify builds, redirects, environment variables, and serverless functions for static sites.

Community
Intermediate
netlifynetlify
32

netlify-caching

Configure and validate Netlify CDN and browser caching headers.

Official
Intermediate
MacPhobosMacPhobos

Netlify Platform Skill

Deploy and manage JAMstack applications on the Netlify platform.

Community
Advanced
lucasilverentandlucasilverentand
3

hono-deployment

Deploy Hono applications across multiple runtimes and hosting platforms.

Community
Advanced