deploy-docs

Validate documentation site completeness and generate GitHub Pages workflow YAML.

1|Updated Apr 4, 2026
One-click install
npx skills add https://github.com/ybbms777/compound-engineering --skill deploy-docs-ybbms777
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: deploy-docs
Source: https://github.com/ybbms777/compound-engineering/tree/main/skills/deploy-docs
Command: npx skills add https://github.com/ybbms777/compound-engineering --skill deploy-docs-ybbms777

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Deploying documentation to GitHub Pages frequently fails due to missing required HTML files, invalid JSON configuration, or incorrect workflow permissions, leading to wasted time troubleshooting deployment errors.

Core Features & Use Cases

  • Documentation Validation: Checks for the existence of all required HTML pages, validates JSON configuration file syntax, and confirms component counts match expected values.
  • Uncommitted Change Detection: Warns users if there are pending changes to documentation files that need to be committed before deployment.
  • Deployment Setup Guidance: Provides step-by-step first-time setup instructions and the exact GitHub Actions workflow YAML required for compliant GitHub Pages deployment with correct permissions.
  • Use Case: For example, if you maintain an open source plugin's documentation, use this Skill to quickly verify all docs pages are present and get the exact workflow configuration needed to auto-deploy updates whenever you push changes to the main branch.

Quick Start

Use the deploy-docs skill to validate your documentation site and receive the exact GitHub Pages deployment workflow configuration required for automated deployments.

Frequently Asked Questions about deploy-docs

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

FAQPage Schema
How do I validate documentation before deploying to GitHub Pages?

To validate documentation for GitHub Pages, you need to check required HTML page existence, confirm JSON configuration syntax validity, and verify component counts match expected values to prevent deployment failures.

What is the correct GitHub Actions workflow YAML for deploying static sites to GitHub Pages?

A compliant GitHub Pages deployment workflow YAML requires correct permissions and concurrency settings to automate static HTML document publishing whenever changes are pushed to the main branch.

Why does my GitHub Pages deployment fail due to uncommitted documentation changes?

GitHub Pages deployment can fail when uncommitted documentation changes exist locally; detecting and warning about pending file modifications ensures only fully committed static HTML updates are deployed.

Can I use GitHub Actions to automate open source documentation deployment?

Yes, you can use GitHub Actions to automate open source documentation deployment by provisioning a workflow YAML that validates static site completeness and auto-publishes updates upon pushing to the main branch.

Does automated documentation deployment require validating JSON configuration syntax?

Yes, automated documentation deployment requires validating JSON configuration syntax because invalid configuration files frequently cause static site deployment errors on GitHub Pages and waste troubleshooting time.