← ClaudeAtlas

github-pages-improvelisted

Propose GitHub Pages improvements for approval before any edits, then coordinate the approved changes. Use for an explicitly staged workflow and for resuming approved GP- IDs; immediate changes go to github-pages-create.
ValentinNikolaev/agent-skills · ★ 1 · AI & Automation · score 74
Install: claude install-skill ValentinNikolaev/agent-skills
# GitHub Pages: Improve Turn an existing Pages site into a reviewable improvement program, then apply only the changes the user selects. ## Enforce the two-phase gate Use this two-phase workflow when the user requests proposals before implementation or explicitly invokes this skill. Route a request to improve or redesign immediately to `github-pages-create`; do not introduce an approval gate into work already authorized. If the user has already selected proposals in this session, resume Phase 2 directly. Phase 1 is read-only. Inspect, render, audit, and propose, but do not edit site sources, dependencies, workflows, repository settings, or tracked generated output. Build and preview in a disposable directory when rendering requires generated files. Stop after presenting the requested proposal. Phase 2 begins only after the user explicitly approves all changes or identifies approved proposal IDs. Approval to implement site changes does not authorize commit, push, publication, workflow changes, repository settings, domains, credentials, analytics, or external services unless those actions are separately named. Do not treat “looks good,” “interesting,” or a request for explanation as implementation approval. Resolve ambiguous or conflicting selections before editing. ## Coordinate the Pages family Treat the first three applicable specialists as required Phase 1 passes, not optional hand-offs. Read and apply their instructions so each concern contributes to the shared pro