docs-refresh

Solid

Refresh plugin catalog docs (README, PLUGIN-MAP, d2 diagram) so per-plugin skill/agent counts match disk. Use when fixing count drift or after adding skills.

AI & Automation 48 stars 6 forks Updated today MIT

Install

View on GitHub

Quality Score: 80/100

Stars 20%
56
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# /docs-refresh Refresh this repo's top-level catalog docs so the stated plugin/skill/agent counts and the plugin set match what is actually on disk. The detector is `scripts/check-docs-index.sh`; this skill is the *fixer* that consumes its report. ## When to Use This Skill | Use this skill when... | Use something else when... | |------------------------|----------------------------| | Per-plugin counts in README / PLUGIN-MAP / the d2 diagram drifted | A plugin needs adding/removing — follow CLAUDE.md § Plugin Lifecycle first, then run this | | `check-docs-index.sh` reports `doc_count_drift` / `diagram_count_drift` | You need a generic project's docs synced — that's `documentation-plugin:docs-sync` (wrong layout for this repo) | | The PR gate `Check docs-index drift` failed in CI | Editing rule-index or marketplace set — the audit reports those, but fix them at their source | ## Context - Audit: !`bash scripts/check-docs-index.sh` - README last touched: !`git log --max-count=1 --format='%h %ci' -- README.md` ## Execution Execute this refresh: ### Step 1: Read the drift Run `bash scripts/check-docs-index.sh` (shown in Context). Each `ISSUES:` line names the exact file, line, and the disk-vs-stated count. `STATUS=OK` with `ISSUE_COUNT=0` means nothing to do — stop and report clean. ### Step 2: Apply count fixes For every `doc_count_drift` / `diagram_count_drift` issue, Edit the stated count to the disk count: - `README.md` — the `| **<plugin>** | N | ... |` category...

Details

Author
laurigates
Repository
laurigates/claude-plugins
Created
7 months ago
Last Updated
today
Language
Shell
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Listed

refresh-agent-docs

Use when refreshing, rewriting, syncing, or creating repository agent instruction files such as AGENTS.md, CLAUDE.md, GEMINI.md, Cursor rules, Kiro steering, Roo rules, Codex instructions, or root project context docs.

2 Updated 5 days ago
YosefHayim
AI & Automation Listed

update-docs

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.

37 Updated today
aws-samples
Data & Documents Listed

doc-sync

Detect documentation drift against current code and confirmed decisions, then propose only the smallest accurate doc updates. Never edit docs without explicit human approval. Use when user asks whether docs need updating, code behavior has changed, interfaces or identifiers have changed, or suspected drift needs investigation. For a full-surface audit across all canonical docs, use the bug-hunt skill's full doc-sync audit (explicit request only), not this skill.

0 Updated today
davidleberknight