CI
aiblueprinthq/ai-blueprint
Set up or normalize one project Verify command and matching GitHub Actions checks while preserving existing CI, with an optional local pre-push hook.
Build or audit an isolated Netlify/Vercel-style pull-request preview workflow using GitHub Actions and the project's existing hosting provider.
Install Diy Netlify
$ npx skills add swyxio/skills --skill diy-netlify -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install swyxio/skills diy-netlify --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/swyxio/skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/diy-netlify .claude/skills/diy-netlify && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "diy-netlify" agent skill from https://github.com/swyxio/skills/tree/main/diy-netlify into .claude/skills/diy-netlify/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "diy-netlify", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/swyxio/skills/tree/main/diy-netlifyType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add swyxio/skills --skill diy-netlify -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install swyxio/skills diy-netlify --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/swyxio/skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/diy-netlify .agents/skills/diy-netlify && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "diy-netlify" agent skill from https://github.com/swyxio/skills/tree/main/diy-netlify into .agents/skills/diy-netlify/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "diy-netlify", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add swyxio/skills --skill diy-netlify -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install swyxio/skills diy-netlify --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/swyxio/skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/diy-netlify .cursor/skills/diy-netlify && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "diy-netlify" agent skill from https://github.com/swyxio/skills/tree/main/diy-netlify into .cursor/skills/diy-netlify/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "diy-netlify", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/swyxio/skills.git --path diy-netlify--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add swyxio/skills --skill diy-netlify -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install swyxio/skills diy-netlify --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/swyxio/skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/diy-netlify .gemini/skills/diy-netlify && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "diy-netlify" agent skill from https://github.com/swyxio/skills/tree/main/diy-netlify into .gemini/skills/diy-netlify/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "diy-netlify", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install swyxio/skills diy-netlifyInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add swyxio/skills --skill diy-netlify -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/swyxio/skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/diy-netlify .github/skills/diy-netlify && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "diy-netlify" agent skill from https://github.com/swyxio/skills/tree/main/diy-netlify into .github/skills/diy-netlify/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "diy-netlify", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add swyxio/skills --skill diy-netlify -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install swyxio/skills diy-netlify --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/swyxio/skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/diy-netlify .opencode/skills/diy-netlify && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "diy-netlify" agent skill from https://github.com/swyxio/skills/tree/main/diy-netlify into .opencode/skills/diy-netlify/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "diy-netlify", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
diy-netlify- GitHub stars
- 176
- Token cost
- ~1.1k tokens
- SKILL.md length
- 520 words
- Files
- 2
- Skills in repo
- 89
- Repo updated
- First seen
- Licence
- MIT
At a glance
Build or audit an isolated Netlify/Vercel-style pull-request preview workflow using GitHub Actions and the project's existing hosting provider.
- Works in 7 steps: Detect affected deployable targets… → Build the intended PR or merge context. → Publish to an environment isolated from… → …
- Eligible PRs need separate live preview environments
- SKILL.md covers Preview contract, Trust boundary, Implementation and Verification
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Diy Netlify is an agent skill from swyxio/skills. 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.
Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `agents/openai.yaml`).
It sits in DevOps & Cloud, covering Pull requests and CI/CD. It works with Netlify, GitHub, Vercel and GitHub Actions. The repository describes itself as: Agent skills for Claude Code and other AI agents. The licence is MIT.
When your agent uses it
- Eligible PRs need separate live preview environments
- Stable and immutable URLs
- GitHub reporting
- Affected-target builds
Example prompts
- “/diy-netlify”
Workflow steps
7 steps, taken from the first numbered list in SKILL.md.
- Detect affected deployable targets conservatively, including shared code and
- Build the intended PR or merge context.
- Publish to an environment isolated from production.
- Preserve both a stable PR URL and an immutable deployment identity or URL.
- Maintain one required GitHub check, including a terminal skipped state.
- Create or update one concise PR comment with target, URL, source SHA, and
- Prevent superseded or stale-head work from replacing a newer preview.
What it can do on your machine
Read from SKILL.md and the folder at commit 038ef34. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Diy Netlify loads about 1.1k tokens when it runs. Until then it costs about 107 tokens; SKILL.md has 520 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from swyxio/skills at commit 038ef34, republished under its MIT licence (© swyxio). 520 words, ~1,065 tokens.
Download SKILL.mdSave it as
.claude/skills/diy-netlify/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- diy-netlify
- description
- 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.
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:
- Detect affected deployable targets conservatively, including shared code and lockfile changes.
- Build the intended PR or merge context.
- Publish to an environment isolated from production.
- Preserve both a stable PR URL and an immutable deployment identity or URL.
- Maintain one required GitHub check, including a terminal skipped state.
- Create or update one concise PR comment with target, URL, source SHA, and status.
- 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.
If the requested design intentionally uses production configuration or reuses a staged version for production, this skill no longer applies. Use the relevant production-release and provider guidance instead.
Show full SKILL.md (277 more words)Show less
Implementation
Start from the repository's existing CI and release authorities. Add the smallest affected-target, build, publication, check, and comment changes needed for the preview contract.
Measure current job and step times before optimizing. Optimize demonstrated bottlenecks without weakening tests. Sparse checkout, filtered installs, runner-provided browsers, caching, and tighter timeouts are optional techniques, not required architecture; exercise every affected matrix target after changing checkout or dependency boundaries.
For Cloudflare-backed previews, consider provider-native hot paths before
starting Wrangler once per item: direct R2 REST uploads with an existing
preview-scoped token or an R2 binding, D1 batches, KV bulk writes, Queue
sendBatch(), and direct Workers API readbacks. Use bounded concurrency and
retries; preserve immutable identities, publication ordering, and preview-only
credentials. Do not add S3 credentials or broaden permissions merely to upload
objects.
Keep production independent: deploy the exact merged SHA through the existing
release authority, then verify provider identity and the owning live hostname.
Pair with cloudflare-production-builder when changing production traffic,
bindings, routes, migrations, promotion, or rollback.
Verification
Use a small visible canary and prove:
- affected targets were selected correctly;
- required source checks passed;
- the PR check and comment point to the latest successful preview;
- the preview renders on the required browser and viewport surfaces;
- merging triggers production for the exact merge SHA; and
- provider readback, the public hostname, and production smoke agree.
When performance is part of the request, report baseline sample size and median/tail timing alongside the canary result. Distinguish wall time, runner minutes, reliability, review experience, and production safety.
Do not add a deployment dashboard, generalized preview database, branch-environment framework, multi-provider abstraction, or resumable release controller without a demonstrated product requirement.
© swyxio, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 1 other file in diy-netlify of swyxio/skills.
- SKILL.md
- agents/openai.yaml
Open the folder on GitHubat commit 038ef34
Compare with similar skills
Diy Netlify next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Diy Netlify this skillswyxio/skills | 176 | — | ~1.1k | Automated safety check: Pass | MIT | |
| CIaiblueprinthq/ai-blueprint | 463 | — | ~2.2k | Automated safety check: Pass | MIT | |
| Michel Monitor Pull Request GitHub ActionsPackmindHub/packmind | 318 | — | ~2.6k | Automated safety check: Pass | Apache-2.0 | |
| CIopenJiuwen-ai/sciencediscovery | 159 | — | ~2.2k | Automated safety check: Pass | Apache-2.0 | |
| ONNX Runtime CI Managementmicrosoft/onnxruntime | 22k | — | ~4.1k | Automated safety check: Pass | MIT | |
| Use Vercel Actionamondnet/vercel-action | 764 | — | ~2.7k | Automated safety check: Pass | MIT |
Similar skills
Michel Monitor Pull Request GitHub Actions
PackmindHub/packmind
Diagnose a failed, stuck, or never-triggered CI run on a GitHub PR, apply a local fix if possible, push it, and document the result in a single running PR comment.
CI
openJiuwen-ai/sciencediscovery
Read, diagnose, and change the CI pipeline: GitHub Actions on pull requests, the nightly schedule and the release tag.
- Official
ONNX Runtime CI Management
microsoft/onnxruntime
Triggers, re-runs and unblocks the CI checks on an ONNX Runtime pull request, after diagnosing whether a failure is transient or needs a code change.
Use Vercel Action
amondnet/vercel-action
Wire amondnet/vercel-action into a GitHub Actions workflow to deploy Vercel projects from CI.
Renovate Actions PR Review
backnotprop/plannotator
Reviews Renovate pull requests that bump GitHub Actions by checking pinned SHAs against upstream tags, scanning changelogs and confirming workflows stay compatible.
More from swyxio/skills
All 89 skills in this repoProgrammatic Agents
swyxio/skills
Run a selected coding-agent CLI programmatically, with latency, error, usage, cost, and trace logging.
Reserved Handle Policy
swyxio/skills
Design, implement, audit, or refresh protected username and handle namespaces for public products.
New Mac Setup
swyxio/skills
Fully automated new Mac setup for fullstack web developers and AI engineers.
Youtube API
swyxio/skills
Manage YouTube videos programmatically via the YouTube Data API v3 — upload video files, upload custom thumbnails, update video metadata (titles, descriptions, tags), and query video/channel info…
Youtube Studio Batch Upload
swyxio/skills
Batch YouTube Studio upload workflow for videos sourced from Airtable, Google Drive, Loom, YouTube, or local files.
Deep Trajectory Analysis
swyxio/skills
Reconstruct and visually analyze paired agent, game, or policy trajectories to determine whether changed actions produced their intended effects.
Related
Works with
Categories
Questions about Diy Netlify
What does Diy Netlify do?
Build or audit an isolated Netlify/Vercel-style pull-request preview workflow using GitHub Actions and the project's existing hosting provider. Diy Netlify is an agent skill from swyxio/skills. Build or audit an isolated Netlify/Vercel-style pull-request preview workflow using GitHub Actions and the project's existing hosting provider.
When should I use Diy Netlify?
Diy Netlify fits situations like: eligible PRs need separate live preview environments; stable and immutable URLs; GitHub reporting; affected-target builds.
How do I install Diy Netlify in Claude Code?
Run `npx skills add swyxio/skills --skill diy-netlify -a claude-code`. Or copy the skill folder (diy-netlify in swyxio/skills) into .claude/skills/diy-netlify in your project. Claude Code loads it when a task matches its description.
How do I install Diy Netlify in Codex?
Run `npx skills add swyxio/skills --skill diy-netlify -a codex`. Or copy the skill folder (diy-netlify in swyxio/skills) into .agents/skills/diy-netlify in your project. Codex loads it when a task matches its description.
Can I use Diy Netlify in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add swyxio/skills --skill diy-netlify -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/diy-netlify, .gemini/skills/diy-netlify, .github/skills/diy-netlify and .opencode/skills/diy-netlify in your project.
What does Diy Netlify need to run?
SKILL.md names no scripts, command-line tools or credentials: Diy Netlify is instructions for the agent only.
Does Diy Netlify access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Diy Netlify safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Diy Netlify use?
Diy Netlify is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Diy Netlify use?
About 1.1k tokens (SKILL.md is roughly 4.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Diy Netlify?
Skills that share tags, products or a category with Diy Netlify: CI (aiblueprinthq/ai-blueprint, 463 stars), Michel Monitor Pull Request GitHub Actions (PackmindHub/packmind, 318 stars), CI (openJiuwen-ai/sciencediscovery, 159 stars) and ONNX Runtime CI Management (microsoft/onnxruntime, 22k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Diy Netlify?
swyxio (a GitHub user) maintains it in swyxio/skills, which has 176 GitHub stars. The repository holds 89 skills in this directory. The repository was last updated on October 5, 2026.
Source: swyxio/skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.