What problem does it solve? A GitHub repository gets only one Pages site, so adding a second site on its own custom domain requires a separate receiving repository, a deploy key, DNS records, a scoped publish run, and Pages configuration — a multi-system process where a single misstep can take down the sites already live. ## Core Features & Use Cases - Receiving repository setup: Creates the public target repository, generates an ed25519 deploy key, and stores the private half as a secret without persisting it locally. - DNS handover and verification: Produces the exact A, AAAA, and CNAME records for the operator's registrar, flags conflicting parking-page records, and verifies resolution from the container without dig. - Scoped pre-merge publish: Dispatches the deploy workflow for one named site only, confirming other sites' jobs are skipped so an unmerged branch cannot republish them. - Use Case: A repository already serving vovazakharov.com adds latestageagentic.com; the skill stands up the receiving repo, DNS, publish run, and Pages settings, then verifies both domains serve their own content. ## Quick Start Ask the agent to stand up the new site on its domain by running /stand-up-site example.com from the branch that builds it.
