docs-publish-github-pages

Inspect and patch GitHub Pages docs publishing workflows.

19|2|Updated Mar 14, 2025

Search Tags:#workflow #validation #deploy #ci-cd #pages #github-pages #docs-publish

Ready to run

npx skills add https://github.com/ThalesGroup/agilab --skill docs-publish-github-pages

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: docs-publish-github-pages
Source: https://github.com/ThalesGroup/agilab/tree/main/.claude/skills/docs-publish-github-pages
Command: npx skills add https://github.com/ThalesGroup/agilab --skill docs-publish-github-pages

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Review, fix, and validate docs publishing workflows for GitHub Pages. Use this skill when a user needs a docs deploy workflow corrected, wants versioning behavior explained, needs publish triggers adjusted, or wants a Pages deployment flow verified end to end.

Core Features & Use Cases

Inspect docs-publish.yaml workflow triggers and Pages enablement to ensure the site is published from the intended source.
Verify that the workflow run succeeds and that Pages is enabled, with a clear distinction between the published site version and the git tag or package version.
Patch triggers, gating logic, and deployment steps only after validating the current deploy path, with a preference for validating published HTML pages over inferred asset URLs.

Quick Start

Identify the repository and Pages site, then review the docs-publish.yaml workflow and validate the published HTML pages.

Frequently Asked Questions about docs-publish-github-pages

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I fix GitHub Pages deployment workflows that fail to publish?▼

Fix GitHub Pages deployment workflows by validating the deploy path, verifying Pages is enabled, and patching triggers, gating logic, and deployment steps in your docs-publish.yaml file to ensure correct site publication. Apply patches only after confirming the current deploy path.

Why does my published GitHub Pages site show the wrong version?▼

Published GitHub Pages sites may show wrong versions when deploy triggers mismatch the intended source. Validate the workflow to distinguish between the published site version and the git tag or package version, ensuring the site publishes from the correct branch or workflow.

How to validate published HTML pages for GitHub Pages deployments?▼

Validate published HTML pages for GitHub Pages deployments by directly inspecting the live site content rather than inferring asset URLs. Identify the repository and Pages site, review the docs-publish.yaml workflow, and confirm the published site matches the intended version.

Does my GitHub Pages deploy workflow need Pages explicitly enabled?▼

GitHub Pages deploy workflows require Pages to be explicitly enabled to ensure the site is published from the intended source. Inspect the docs-publish.yaml workflow triggers and Pages enablement settings to verify the workflow run succeeds and deployment completes correctly.

What is the best way to adjust publish triggers for GitHub Pages documentation?▼

The best way to adjust publish triggers for GitHub Pages documentation is to patch triggers, gating logic, and deployment steps after validating the current deploy path. Ensure the workflow distinguishes the published site version from the git tag or package version.

When should I not use inferred asset URLs for GitHub Pages validation?▼

Avoid using inferred asset URLs for GitHub Pages validation when you need to confirm site integrity. Instead, validate the published HTML pages directly to ensure the deployed site matches the intended version and that the workflow run succeeds end to end.