Diy Netlify

Build or audit an isolated Netlify/Vercel-style pull-request preview workflow using GitHub Actions and the project's existing hosting provider. Use when eligible PRs need separate live preview environments, stable and immutable URLs, GitHub reporting, affected-target builds, and safe fork handling. Do not use for production-bound staged versions, artifact promotion or reuse, or generalized release-platform design.

201 stars 12 forksDevOps & Cloud

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add swyxio/skills --skill diy-netlify
Manual install
git clone --depth 1 https://github.com/swyxio/skills.git /tmp/skills
mkdir -p ~/.claude/skills
cp -r /tmp/skills/diy-netlify ~/.claude/skills/diy-netlify

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# DIY Netlify

Deliver the reviewer loop people expect from hosted deploy previews without
recreating a deployment platform:

> Open a PR, wait for the preview link, review it, merge when green, and let the
> exact merge commit deploy to production.

## Preview contract

For each eligible PR:

1. Detect affected deployable targets conservatively, including shared code and
   lockfile changes.
2. Build the intended PR or merge context.
3. Publish to an environment isolated from production.
4. Preserve both a stable PR URL and an immutable deployment identity or URL.
5. Maintain one required GitHub check, including a terminal skipped state.
6. Create or update one concise PR comment with target, URL, source SHA, and
   status.
7. Prevent superseded or stale-head work from replacing a newer preview.

Add `noindex` when the hosting layer does not already provide it. Add a
changed-route entry link only when it can be derived reliably.

## Trust boundary

For same-repository PRs, use dedicated preview Workers, projects, namespaces,
and preview-safe configuration. Do not give preview code production routes,
secrets, data, or service bindings.

Exclude forks unless they have a separately authorized, sandboxed publication
path. Never expose protected credentials to untrusted workflow code.

Treat source checks, preview deployment, merged source, production deployment,
traffic, and live behavior as separate facts. A successful preview is not
production proof.
Read the full skill on GitHub

Details

Skill name
diy-netlify
Repository
swyxio/skills
Path
diy-netlify/SKILL.md
License
MIT
Repo updated
16 November 2026

FAQ

What does the Diy Netlify skill do?

Build or audit an isolated Netlify/Vercel-style pull-request preview workflow using GitHub Actions and the project's existing hosting provider. Use when eligible PRs need separate live preview environments, stable and immutable URLs, GitHub reporting, affected-target builds, and safe fork handling. Do not use for production-bound staged versions, artifact promotion or reuse, or generalized release-platform design.

How do I install the Diy Netlify skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add swyxio/skills --skill diy-netlify. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Diy Netlify popular?

It lives in swyxio/skills, which has 201 GitHub stars and 12 forks.

Related skills

Accelevents API

201

swyxio/skills

Use when reading or updating AI Engineer Europe speaker records through the Accelevents REST API, especially for full-record PUT updates, auth header quirks, and preserving existing speaker fields.

Software Development12

Accelevents Speaker Sync

201

swyxio/skills

Use when website speaker, session, schedule, room, track, or headshot changes must be synchronized back to Accelevents for AI Engineer Europe 2026.

AI, LLMs & Agents12

Agents SDK

201

swyxio/skills

Build or debug stateful applications that specifically use Cloudflare's `agents` package, including Agent classes, routing, callable methods, synchronized state, scheduling, AIChatAgent, durable execution, or Agents SDK client hooks. Do not trigger for generic AI-agent design, the OpenAI Agents SDK, or ordinary Durable Object work that does not use the Cloudflare Agents SDK.

AI, LLMs & Agents12

Dns Zonefile Config

150

guia-matthieu/clawfu-skills

Configurez correctement vos zones DNS pour l'email deliverability (SPF, DKIM, DMARC), la sécurité (DNSSEC, CAA), et l'automatisation (OVH API, Cloudflare, Terraform), basé sur les best practices 2024-2025. Use when: **Configurer l'authentification email** - SPF, DKIM, DMARC pour éviter le spam folder; **Sécuriser un domaine** - DNSSEC, CAA records, protection contre le spoofing; **Automatiser la gestion DNS** - OVH API, Cloudflare API, Terraform; **Débugger des problèmes DNS** - dig, nslookup...

DevOps & CloudIn 1 list32

Devcontainer

191

jwynia/agent-skills

Diagnose devcontainer configuration problems and guide development environment setup. This skill should be used when the user asks to 'set up devcontainer', 'fix container startup', 'configure VS Code dev container', 'Codespaces setup', or has Docker development environment issues. Keywords: devcontainer, docker, VS Code, Codespaces, container, development environment, Dockerfile.

DevOps & Cloud24

Dockerfile Optimise

228

pproenca/dot-skills

Dockerfile optimization guidelines from official Docker documentation. This skill should be used when writing, reviewing, or refactoring Dockerfiles to ensure optimal build time, image size, security, and robustness. Triggers on tasks involving Dockerfile creation, Docker image builds, container optimization, multi-stage builds, build cache, or Docker security hardening.

DevOps & Cloud19

Browse the most popular Claude skills, all devops & cloud skills, or write your own with the skills generator.