Individual skill
post-launch
The moment DNS moves and for the thirty days after — verifies the cutover (DNS propagation, certificate, http and www redirects, the noindex, robots and sitemap on the live host, every redirect the audit mapped, forms, analytics, the staging copy, the old host, security headers), diffs production against the pre-launch baseline, and schedules the watch. Use when asked did the launch work, is the site live, what should I check after launch, the domain just switched, or when a site went live in the last month and something looks wrong. It is read-only and exits 0 whatever it finds.
skills/post-launch/SKILL.md
Source commit 8beb1de5099a2be1ddb1d98ffc7b3682343bc420
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Network or broad shell
- Last checked
- Nov 6, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 123
- Repository last updated
- Oct 31, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- agent-skills Repository topic
- ai-agents Repository topic
- astro Repository topic
- claude-code Repository topic
- cloudflare-pages Repository topic
- codex Repository topic
- jamstack Repository topic
- playwright Repository topic
- seo Repository topic
- site-migration Repository topic
- security Derived category
- data Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 9,185 bytesSKILL.mdcore · 9,185 bytesreferences/baseline-diff.mddoc · 5,383 bytesreferences/cutover-day.mddoc · 9,159 bytesreferences/reading-the-report.mddoc · 5,794 bytesreferences/thirty-day-watch.mddoc · 5,728 bytesscripts/lib/checks/cutover.mjsruns · 47,096 bytesscripts/lib/cutover.mjsruns · 26,807 bytesscripts/lib/plan.mjsruns · 5,658 bytesscripts/lib/watch.mjsruns · 6,832 bytesscripts/post-launch.mjsruns · 15,077 bytes
Read excerpt
# post-launch
The watch. It runs the moment DNS has moved, and then once a day for thirty days. It reports; it
never gates, never fixes, and never announces anything.
## The one rule
**Blockers are read first and announced last.** Nothing about a launch is announced — no email, no
post, no client call — until this report comes back clean. An announcement is the only step of a
launch that cannot be taken back, and the two blockers here are exactly the two states where the
launch has not really happened: a certificate nobody can get past, and a noindex telling search
engines to forget the site. Both look fine in a browser you are already logged into.
If somebody asks you to announce while a blocker stands, say plainly what the blocker is and what