← ClaudeAtlas

github-pages-auditlisted

Audit a rendered GitHub Pages site or production-equivalent build and report UX and accessibility findings without edits. Use for Pages verification, not source-only review or implementation.
ValentinNikolaev/agent-skills · ★ 1 · AI & Automation · score 74
Install: claude install-skill ValentinNikolaev/agent-skills
# GitHub Pages: Audit Evaluate the rendered Pages experience against repository evidence and real reader tasks. This pass stays read-only. Return requested fixes to `github-pages-create`, or to `github-pages-improve` for its existing proposal/approval state. ## Establish the audit target - Confirm the site is GitHub Pages or a production-equivalent local build with the same base path and output. - Resolve the repository/build path and preview URL before testing. If the rendered target cannot be identified or started safely, request that target and report the audit as not run rather than substituting source inspection. - Inspect repository branding, documented reader tasks, current site configuration, route expectations, and any explicit design tokens or content rules. - Record the exact build, URL or local preview, viewport sizes, theme, browser, and available accessibility tooling. - Check the build against the current relevant source snapshot using the family's [handoff contract](../github-pages-create/references/workflow-handoffs.md). Build or preview in a disposable directory when an audit requires generated files, preserving site sources and tracked output. - Do not claim rendered, keyboard, contrast, or screen-reader verification when only source files were inspected. ## Read the checklist Read [references/rendered-pages-audit.md](references/rendered-pages-audit.md) before performing the audit. For visual coherence and repeated composition patterns, use the visual