configure-plugin/skills/configure-github-pages/SKILL.md
GitHub Pages deployment workflows for docs sites. Use when setting up Pages, migrating to actions/deploy-pages, or auditing Pages action versions.
npx skillsauth add laurigates/claude-plugins configure-github-pagesInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Check and configure GitHub Pages deployment.
| Use this skill when... | Use another approach when... |
|------------------------|------------------------------|
| Setting up GitHub Pages deployment for a documentation site | Configuring documentation standards or generators (/configure:docs instead) |
| Creating or updating a GitHub Actions workflow for Pages deployment | Debugging a failed GitHub Actions workflow (/configure:workflows instead) |
| Migrating from peaceiris/actions-gh-pages to official actions/deploy-pages | Editing documentation content or markdown files |
| Auditing Pages workflow for outdated action versions or missing permissions | Setting up a custom domain via DNS (manual repository settings) |
| Adding Pages deployment to a project with an existing doc generator | Configuring CI/CD workflows unrelated to documentation |
find .github/workflows -maxdepth 1 \( -name '*doc*.yml' -o -name '*pages*.yml' \)find . -maxdepth 1 \( -name 'mkdocs.yml' -o -name 'typedoc.json' -o -name 'docusaurus.config.*' \)find . -maxdepth 1 -type d \( -name 'docs' -o -name 'site' \)find . -maxdepth 1 -name 'CNAME'find . -maxdepth 1 -name '.project-standards.yaml'Parse from command arguments:
--check-only: Report compliance status without modifications (CI/CD mode)--fix: Apply fixes automatically without prompting--source <docs|site|custom>: Override source directory detectionExecute this GitHub Pages deployment configuration check:
Identify existing documentation configuration:
| Config File | Generator | Output Directory |
|-------------|-----------|------------------|
| typedoc.json | TypeDoc | docs/ or configured |
| mkdocs.yml | MkDocs | site/ |
| docs/conf.py | Sphinx | docs/_build/html/ |
| docusaurus.config.js | Docusaurus | build/ |
| Cargo.toml (with rustdoc) | rustdoc | target/doc/ |
| None | Static | docs/ |
If no documentation configured, report:
No documentation generator detected.
Consider running /configure:docs first to:
- Set up documentation linting standards
- Configure a documentation generator
Would you like to:
[A] Configure documentation first (/configure:docs)
[B] Set up static HTML hosting for existing docs/ directory
[C] Skip - I'll configure docs later
Check for existing GitHub Pages workflows by searching for:
actions/deploy-pagesactions/upload-pages-artifactpeaceiris/actions-gh-pagesExtract from existing workflow: current action versions, permissions, build steps, source directory.
Validate GitHub Actions workflow against standards:
| Check | Standard | Severity |
|-------|----------|----------|
| actions/deploy-pages | v5+ | WARN if older |
| actions/configure-pages | v6+ | WARN if missing |
| actions/upload-pages-artifact | v5+ | WARN if older |
| Permissions | pages: write, id-token: write | FAIL if missing |
| Environment | github-pages | WARN if missing |
| Concurrency | Group defined | INFO |
Print a formatted compliance report:
GitHub Pages Compliance Report
==============================
Project: [name]
Documentation Status:
Generator [typedoc|mkdocs|sphinx|rustdoc|static|not configured]
Source directory [docs/|site/|custom]
Build command [detected command or "not configured"]
GitHub Pages Workflow:
Workflow file .github/workflows/docs.yml [EXISTS | MISSING]
Workflow Checks (if exists):
deploy-pages v5 [PASS | OUTDATED | MISSING]
configure-pages v6 [PASS | MISSING]
upload-artifact v5 [PASS | OUTDATED]
Permissions pages: write, id-token [PASS | MISSING]
Environment github-pages [PASS | MISSING]
Overall: [X issues found]
Recommendations:
[List specific fixes needed]
If --check-only, stop here.
Create .github/workflows/docs.yml based on detected generator. Use the appropriate workflow template from REFERENCE.md:
./docs./site./docs/_build/html./target/doc./docs directoryAll workflows include:
pages: write, id-token: write)workflow_dispatch for manual triggersUpdate .project-standards.yaml:
standards_version: "2025.1"
last_configured: "[timestamp]"
components:
github-pages: "2025.1"
github-pages-generator: "[typedoc|mkdocs|sphinx|rustdoc|static]"
github-pages-source: "[docs/|site/|custom]"
GitHub Pages Configuration Complete
===================================
Workflow created: .github/workflows/docs.yml
Next Steps:
1. Enable GitHub Pages in repository settings:
Settings -> Pages -> Source: GitHub Actions
2. Push to main branch to trigger deployment:
git add .github/workflows/docs.yml
git commit -m "ci(docs): add GitHub Pages deployment workflow"
git push
3. After deployment, your docs will be available at:
https://OWNER.github.io/REPO/
Optional:
- Add custom domain: Create CNAME file with your domain
- Protect deployment: Configure environment protection rules
For detailed workflow templates, see REFERENCE.md.
Provide:
| Context | Command |
|---------|---------|
| Quick compliance check | /configure:github-pages --check-only |
| Auto-fix all issues | /configure:github-pages --fix |
| Check Pages workflow exists | find .github/workflows -name '*pages*' -o -name '*doc*' 2>/dev/null |
| Check Pages action versions | grep -E 'deploy-pages|upload-pages-artifact|configure-pages' .github/workflows/*.yml |
| Verify Pages enabled | gh api repos/{owner}/{repo}/pages --jq '.status' |
| Check deployment status | gh api repos/{owner}/{repo}/pages/builds --jq '.[0].status' |
/configure:docs - Set up documentation standards and generators/configure:workflows - GitHub Actions workflow standards/configure:all - Run all compliance checks/configure:status - Quick compliance overviewtools
Scaffold a new ComfyUI custom-node repo (pyproject, CI, release-please, vitest+pytest, JS extension skeleton) in the picker/gesture vein. Use when bootstrapping or init-ing a comfyui node pack.
tools
Orchestrate a ComfyUI node pack from idea to registry: scaffold, create + seed the repo, open the gitops adoption PR. Use when releasing or spinning up a new comfyui node pack.
testing
macOS EndpointSecurity/EDR high CPU & battery drain. Use when Kandji ESF / XProtect pegs a core; trace the exec storm via powermetrics + eslogger.
development
odiff pixel-by-pixel image diffing. Use when comparing screenshots, detecting visual regressions, diffing before/after PNGs, asserting golden images.