update-docslisted

Audit and update every documentation surface in the APEX repo against the current state of skills, steering workflows, README marker tables, and the Docusaurus site under misc/website/. After any change to a skill (rename, retire, add, edit description), walk the repo, re-run script-managed surfaces if their --check fails, and reason through every tracked prose *.md to catch references that need updating. Use after adding/removing/renaming a skill, after editing SKILL.md frontmatter, after editing README marker blocks, or before publishing a docs change. Also use when the user says "update docs", "sync docs", "check docs", "run update-docs", or mentions that documentation might be stale.
aws-samples/sample-apex-skills · ★ 37 · AI & Automation · score 73

Install: claude install-skill aws-samples/sample-apex-skills

# Update Docs Walk the APEX repo after any content change and bring every documentation surface back into sync. Two categories of surface exist: script-managed (deterministic, re-runnable) and prose (requires reasoning). Handle both in a single pass. ## When to use - A skill was added, removed, renamed, or had its frontmatter edited - A steering workflow was added, removed, or renamed - README marker blocks were edited manually - Before opening a PR that touches `skills/` or `steering/` - The user asks to "check docs", "update docs", or "sync documentation" ## Modes **Coding-agent mode** (default in Claude Code): walk the repo, re-run scripts, propose diffs, ask before writing user-facing prose. Auto-apply mechanical fixes (script outputs, simple name substitutions in fenced code blocks). **Chat-only mode** (no file-write tools available): emit the PASS/STALE table + a fix checklist of one-line commands. No file edits. ## Step 1: Detect the change set Determine what changed. Default comparison base is `origin/main`: ```bash git diff --name-status origin/main...HEAD -- 'skills/**/SKILL.md' 'steering/workflows/*.md' 'steering/commands/**/*.md' 'devops-agent/**' ``` If the user specifies a different scope ("since my last commit", "just the rename I did"), adjust the base accordingly. Also include any paths the user explicitly names. ## Step 2: Tier 1 — Script-managed surfaces Two scripts own deterministic regeneration. Detect staleness and re-run them. Never duplicat