1. Habit
  2. Skills
  3. Netlify Config skill
netlify · 3K installs

Netlify Config skill
Runs by itself, netlify config changes.

Netlify config changes ship without surprises.

Install the Netlify Config skill and make it a habit: follow https://gethabit.dev/skills/netlify/netlify-config.md

  1. 1Copy
  2. 2Paste into Claude Code, Codex or Cursor
  3. 3It runs by itself

3K installs41 starsMIT licenceSource on GitHub ↗

Netlify Config

by netlify · 3K installs

The skill

The netlify config skill configures Netlify builds and routing through netlify.toml, _redirects and _headers: build commands, redirects and proxies, SPA fallback, custom headers, env vars and secrets, ignore builds and monorepos.

Only when you ask.

The habit

Netlify config changes ship without surprises.

↻ Runs by itselfnetlify config changes

How the habit works.
You don't have to.

Three questionsWhen does it start? How does it check its work? What does it remember?

01

It starts by itself

netlify config changes. Runs in GitHub Actions or Claude Code routine.

  • ↻ netlify config changes
  • pull request touching netlify.toml, _redirects or _headers

02

It checks its work

config rules hold. If a check fails, it tries again.

  • ✓no 307 status in redirects
  • ✓no $VAR injection in netlify.toml outside signed proxies
  • ✓no secrets in client-prefixed env vars
  • ✓netlify build passes

03

It remembers

config findings log. The next run reads it first: rules that failed in earlier changes.

loops/netlify-config-review-loop/run-log.md

One run, step by step.
Then it stops.

Stop ruleStops after one change set per run, with at most 2 fix retries.

  1. 01

    Read config

    Your agent reads netlify.toml, _redirects and _headers from the root or base directory.

  2. 02

    Check redirects

    It checks rule order, splats at segment ends, the SPA fallback and no trailing-slash loops.

  3. 03

    Check headers

    It confirms headers are global and not expected on function or proxied responses.

  4. 04

    Check env vars

    It keeps secrets in the UI or CLI, marks them --secret, and keeps .env gitignored.

  5. 05

    Build

    It runs netlify build locally to confirm the config works.

What it may do.
Nothing more.

Safe by defaultIt writes only in its own folder and asks you before anything goes out.

Is it for you?
Use it when it fits.

Quick checkRead both lists. If the left one sounds like you, the Netlify Config skill helps.

Use it when

  • ✓ adding redirects or an SPA fallback
  • ✓ scoping env vars per deploy context
  • ✓ configuring a monorepo build

Skip it when

  • – you host elsewhere
  • – you only write serverless functions

Questions

Netlify Config skill, answered.

Do env vars in netlify.toml reach functions?

No. The skill says they are not available to functions at runtime; set those in the UI or with netlify env:set.

Which redirect rules run first?

_redirects rules run before netlify.toml, and in each the first match from the top wins.

How do I install the Netlify Config skill?

Copy the prompt at the top into your agent. It installs the skill from netlify/context-and-tools and sets up the habit. Or run npx skills add netlify/context-and-tools --skill netlify-config.

Is the Netlify Config skill free?

Yes. It is published under MIT. Habit is free too.

Netlify Config. Now as a habit.

Install the Netlify Config skill and make it a habit: follow https://gethabit.dev/skills/netlify/netlify-config.md

  • Free
  • No account
  • Undo in one line

All netlify skills →More ops skills →

Works in

  • Claude Code
  • Codex
  • Cursor
  • ChatGPT
  • Claude app

Made by netlify, published under MIT. Habit links to the original and never changes it. Is this your skill?

Copying didn't work here. Select the line and copy it by hand.