GitHub Pages Publish

Put a website live on GitHub Pages and hand back a URL that was checked live. The input is the content (text, one HTML file, or a folder of ready files) and the target repo, which can differ from the repo the user is working in. The skill creates or repairs a GitHub Actions deploy workflow, sets Pages to deploy from Actions, pushes to the default branch, and proves the live site serves the committed bytes. Automate every step. Stop only at a confirmation gate.

Terms used throughout:

• target repo: owner/name that hosts the site. A bare name means the gh user's account.
• content: the files to publish, staged in <work>/content/ before anything is pushed.
• workspace: the checkout that receives the commit. It is the current checkout (in-place) or a clone in <work>/repo/.
• site folder: the folder inside the workspace that Pages deploys: ., docs, or the user's choice.
• confirmation gate: one of the questions listed in Step 2. Nothing else stops the run.
• pre-authorized: the request already answers a gate ("create it if needed", "make it public"). State the answer in one line and continue.
• live check: verify passes, which means every checked file at the Pages URL matches the committed file byte for byte.
• run log: .pages-publish/run-<UTC>.md in the current directory. Every step appends one row.