Deploy sites, configure serverless and edge functions, and verify builds on Netlify. Use when the user mentions: 'deploy preview', 'configure netlify.toml', or 'debug a failed deploy'. Trigger terms: build error, Netlify Functions, deploy logs, deploy preview
100
100%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Netlify-specific deployment patterns and conventions. For project-specific deployment architecture, environment variables, and key files, see deployment-config.md.
| Branch | Environment |
|---|---|
main | Production (auto) |
feature/*, fix/* | Deploy preview (auto, unique URL) |
netlify.toml (build command, publish dir, env vars).netlify build --debug — fix any errors before pushing.curl -fsS -o /dev/null -w '%{http_code}' https://<DEPLOY_URL>/ — expect 200.main — production auto-deploys.[build]
command = "npm run build"
publish = "dist" # or ".next", "out", "build"
[build.environment]
NODE_VERSION = "20"
[[redirects]]
from = "/*"
to = "/index.html"
status = 200
conditions = {Role = ["admin"]}For security headers config, see REFERENCE.md.
Place functions in netlify/functions/. For full examples and CI-ready function patterns see REFERENCE.md.
Config export defines routing (path) instead of the default /.netlify/functions/<name> path.Place edge functions in netlify/edge-functions/:
// netlify/edge-functions/geolocation.ts
import type { Context } from '@netlify/edge-functions';
export default async (request: Request, context: Context) => {
const { country } = context.geo;
return new Response(`You're visiting from ${country}`);
};
export const config = { path: '/geo' };See REFERENCE.md for environment variable scoping and security header examples.
// netlify/functions/daily-task.ts
import type { Config } from "@netlify/functions";
export default async (req: Request) => {
const { next_run } = await req.json();
console.log("Next invocation at:", next_run);
};
export const config: Config = {
schedule: "0 0 * * *", // Daily at midnight UTC
};netlify build --debug # reproduce locally with verbose output
netlify env:list # verify env vars are set
netlify status # check linked site and deploy stateCommon fixes: set NODE_VERSION in netlify.toml, sync lockfile, verify publish directory matches build output.
curl -fsS -o /dev/null -w '%{http_code}' https://<DEPLOY_URL>/ # expect 200
curl -fsS -o /dev/null -w '%{http_code}' https://<DEPLOY_URL>/api/health # expect 200If any route fails: inspect deploy logs in Netlify UI, fix, and re-deploy. See REFERENCE.md for extended verification scripts.
f5c8508
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.