dns-cutover
Skill0 starsChanged 5 months agoMITView on GitHub
Generate the exact DNS records for pointing a custom domain at Vercel, Netlify, Cloudflare Pages, or GitHub Pages — and validate the user's actual records before they flip the domain. Use whenever the user mentions custom domains, DNS, nameservers, 'domain not working', CNAME/A records, or connecting a purchased domain to a deployed site. Runs fully offline — no API keys, no network, no credentials.
In this repository9 other files it gives its agents.
- bundle-weightSkill
- ci-workflow-doctorSkill
- cors-auditorSkill
- deploy-log-doctorSkill
- env-driftSkill
- lockfile-doctorSkill
- migration-reversibilitySkill
- rollback-readinessSkill
- secret-preflightSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 32
All paths below are relative to this skill's directory (dns-cutover/).
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
dns-cutover
Part of shipsafe — offline deploy-safety skills. Every script is stdlib-only Python 3.8+; nothing leaves the machine.
Two modes:
# 1) What records do I need?
python3 scripts/dns_cutover.py plan <domain> <platform>
# 2) Are my records right? (paste zone export or `dig +noall +answer` output into a file)
python3 scripts/dns_cutover.py check <domain> <platform> <records_file> [--json]Platforms: vercel, netlify, cloudflare-pages, github-pages.
check validates apex and www records, and additionally catches the three classic cutover mistakes:
- apex CNAME — illegal on standard DNS, silently breaks MX/email at most registrars
- stale extra A records — round-robin traffic to the dead old host (looks like 'site randomly down')
- conflicting A + CNAME on the same name
Process to walk the user through: lower TTL to 300s the day BEFORE → run plan → set records → export/dig the records into a file → run check → only then flip. After cutover, verify HTTPS on BOTH apex and www — cert issuance is the step that fails silently.
Some values are project-specific (e.g. <yoursite>.netlify.app); the script marks these and the user's dashboard value wins.
Exit codes: 0 ok, 1 problems found.
All paths below are relative to this skill's directory (dns-cutover/).
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.