update-docs
Skill438 starsChanged 53 days agoApache-2.0View on GitHub
Audit and update all documentation moving parts for ai-platform-engineering. Checks release blog posts, features page, agent docs, homepage version strings, Docusaurus version config, and sidebar completeness. Fixes what is stale and reports what needs manual attention. Use after cutting a release, adding a new agent, or updating platform features.
87 other projects use a version of this.
Adopted by
Most recently taken up by
- rmichak/claude-skillstheir own version, first seen Nov 8, 2026
- Eclipter/agentstheir own version, first seen Nov 8, 2026
- rvdbreemen/OTGW-firmwaretheir own version, first seen Nov 8, 2026
- jmusick/skillstheir own version, first seen Nov 8, 2026
- protokol11/skillstheir own version, first seen Nov 8, 2026
- OldemarJesus/connectlife-mcp-servertheir own version, first seen Nov 8, 2026
Used with
Projects with it also use get-pr-reviews, push-everything and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
saffron-healthSkillget-pr-reviews
Get nicely formatted output of the last review comments on a PR. Used internally by other skills.
Also in 3 projects that use this
saffron-healthSkillpush-everything
Stage ALL changes in the repository (not just session changes), commit, and push. Use when you need to commit all pending changes.
Also in 3 projects that use this
TheKREATORSSkillinstinct-export
Export instincts from project/global scope to a file
Also in 3 projects that use this
TheKREATORSSkillinstinct-import
Import instincts from file or URL into project/global scope
Also in 3 projects that use this
NVIDIASkillgenerate-spec
Produce a feature specification covering API changes, backward compatibility, cross-language impact, performance, and a file-level change plan. Use when designing a new feature, planning a significant change, or the user asks to spec something out.
Also in 3 projects that use this
belokonmSkillfullstack-developer
End-to-end feature expert specializing in frontend-backend integration, system architecture, and complete application development
Also in 4 projects that use this
- +1 more from saffron-health
- +1 more from TheKREATORS
Other versions87 projects use a version of this.
Word for word · 1
- cnoe-io/ai-platform-engineering★ 438100% same
Edited · 0
None found.
Wrote their own version · 86
- vercel/next.js★ 143ksame name
- pipecat-ai/pipecat★ 17ksame name
- anyproto/anytype-ts★ 9.1ksame name
- vladmandic/sdnext★ 7.4ksame name
- ArcReel/ArcReel★ 6.3ksame name
- dotnet/sdk★ 3.2ksame name
- meta-pytorch/OpenEnv★ 2.8ksame name
- huggingface/OpenEnv★ 2.8ksame name
- man-group/ArcticDB★ 2.6ksame name
- fabro-sh/fabro★ 1.8ksame name
76 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository21 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .cursor/rules/docker-compose-first-install.mdcCursor rule
- .cursor/rules/safe-git-worktree.mdcCursor rule
- .cursor/rules/specify-rules.mdcCursor rule
- docker-compose-first-installSkill
- local-integration-testingSkill
- release-docsSkill
- run-caipe-integration-testsSkill
- skillsSkill
- speckit.analyzeSkill
- speckit.checklistSkill
- speckit.clarifySkill
- speckit.constitutionSkill
- speckit.implementSkill
- speckit.planSkill
- speckit.specifySkill
- speckit.sync-templateSkill
- speckit.tasksSkill
- speckit.taskstoissuesSkill
- streaming-testingSkill
- ui-performance-benchmarkSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
14 rules. 0 are common, 8 are distinctive, and 6 are very specific to this project.
0
Common
Most of the 80 edited versions we read keep these.
8
Distinctive
This author's own choices. Worth a look.
6
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 43
Run all of the following in parallel.
- Very specific: line 101
If a tag has 0 posts → STALE: call /release-docs for that version, or flag for manual creation.
- Distinctive: line 102
If a post exists → PASS.
- Very specific: line 111
If the Helm --version value ≠ $LATEST → STALE: update HELM_CMD constant and any hardcoded version strings in index.tsx.
- Very specific: line 120
If lastVersion ≠ $LATEST → STALE: update lastVersion in docs/docusaurus.config.ts.
- Very specific: line 128
If versioned_docs/version-$LATEST/ does not exist → STALE: run:
- Very specific: line 195
If the label says X.Y.Z (Latest) but $LATEST ≠ X.Y.Z → STALE: update the label.
- Distinctive: line 216
After all checks and fixes, produce a summary table:
- Distinctive: line 233
If nothing is stale, say so explicitly: "All docs surfaces are up to date."
- Distinctive: line 239
Never delete existing release posts, even for yanked versions.
- Distinctive: line 240
Never auto-write features page tiles — copy must be human-approved.
- Very specific: line 242
If lastVersion is updated, also update the version entry label (e.g.
- Distinctive: line 243
All file writes must follow the project's conventional commit style.
- Distinctive: line 244
If git tag shows no semver tags, report "no versioned releases found" and skip version checks.
“Common” is measured: kept by at least 6 in 10 of the 80 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
update-docs
Audit every documentation surface in ai-platform-engineering and fix what is out of date.
What this skill checks
| # | Surface | Stale when… |
| 1 | Release blog posts | A git tag exists with no matching docs/releases/ file |
| 2 | Homepage version string | Helm --version in docs/src/pages/index.tsx doesn't match latest git tag |
| 3 | Docusaurus version config | lastVersion in docusaurus.config.ts doesn't match latest git tag |
| 4 | Docusaurus version snapshot | A tag exists but no versioned_docs/version-X.Y.Z/ snapshot |
| 5 | Features page | docs/src/pages/features.tsx tiles don't reflect new feature docs in docs/docs/features/ |
| 6 | Agent docs | A directory under ai_platform_engineering/agents/ has no matching docs/docs/agents/<name>.md |
| 7 | Sidebar completeness | A directory under docs/docs/ is not referenced in docs/sidebars.ts |
| 8 | Navbar version label | The 0.4.X (Latest) label in the navbar version dropdown is behind the latest tag |
Execution context
Runs in two modes:
- Coding agent (Claude Code) — runs
git,find,grepdirectly and writes fixes to disk. - Chat-only — renders a checklist of findings; states which files to edit and what to change.
Step 1 — Collect ground truth
Run all of the following in parallel.
# Latest stable git tag
LATEST=$(git tag --sort=-version:refname | grep -E '^[0-9]+\.[0-9]+\.[0-9]+$' | head -1)
echo "Latest tag: $LATEST"
# All release tags
git tag --sort=-version:refname | grep -E '^[0-9]+\.[0-9]+\.[0-9]+$'
# Existing release blog posts (extract version from filename)
ls docs/releases/*.md 2>/dev/null | grep -oE '[0-9]+\.[0-9]+\.[0-9]+' | tr '-' '.'
# Current lastVersion in docusaurus config
grep 'lastVersion' docs/docusaurus.config.ts
# Current Helm version string on homepage
grep -o "'--version [0-9.]*'" docs/src/pages/index.tsx ||
grep -o '"--version [0-9.]*"' docs/src/pages/index.tsx ||
grep 'version' docs/src/pages/index.tsx | grep helm | head -3
# Versioned snapshots
ls docs/versioned_docs/
# Agent implementation directories
ls ai_platform_engineering/agents/
# Agent doc files
ls docs/docs/agents/*.md 2>/dev/null | xargs -I{} basename {} .md
# Feature doc files
ls docs/docs/features/*.md 2>/dev/null | xargs -I{} basename {} .md
# Top-level docs directories
ls -d docs/docs/*/
# Sidebar entries
grep -E "^\s+'[a-z]" docs/sidebars.ts | head -40Step 2 — Run the audit
For each check, produce a PASS ✅ or STALE ⚠️ result.
Check 1 — Release blog posts
Compare every git tag against docs/releases/.
for tag in $(git tag --sort=-version:refname | grep -E '^[0-9]+\.[0-9]+\.[0-9]+$'); do
slug=$(echo $tag | tr '.' '-')
match=$(ls docs/releases/*release-${slug}.md 2>/dev/null | wc -l)
echo "$tag: $match post(s)"
done- If a tag has 0 posts → STALE: call
/release-docsfor that version, or flag for manual creation. - If a post exists → PASS.
Check 2 — Homepage version string
LATEST=$(git tag --sort=-version:refname | grep -E '^[0-9]+\.[0-9]+\.[0-9]+$' | head -1)
grep -n "$LATEST\|--version" docs/src/pages/index.tsx | head -5- If the Helm
--versionvalue ≠$LATEST→ STALE: updateHELM_CMDconstant and any hardcoded version strings inindex.tsx. - Fix: replace every occurrence of the old version string with
$LATEST.
Check 3 — Docusaurus lastVersion
grep 'lastVersion' docs/docusaurus.config.ts- If
lastVersion≠$LATEST→ STALE: updatelastVersionindocs/docusaurus.config.ts.
Check 4 — Versioned snapshot exists
ls docs/versioned_docs/- If
versioned_docs/version-$LATEST/does not exist → STALE: run:
cd docs && npm run docusaurus -- docs:version $LATESTThen update docusaurus.config.ts to add the new version entry and set it as lastVersion.
Check 5 — Features page vs feature docs
# Titles in the features page
grep "title:" docs/src/pages/features.tsx | grep -oP "(?<=')[^']+(?=')"
# Feature doc files that exist
ls docs/docs/features/*.md | xargs -I{} basename {} .md- For each
docs/docs/features/<name>.mdthat has no matching tile infeatures.tsx→ STALE: add a tile. - Report the list; ask the user which new features to add tiles for before editing.
Check 6 — Agent docs coverage
# Agent implementation directories
AGENTS=$(ls -d ai_platform_engineering/agents/*/ 2>/dev/null | xargs -I{} basename {})
# Agent doc files (basename without .md)
AGENT_DOCS=$(ls docs/docs/agents/*.md 2>/dev/null | xargs -I{} basename {} .md)
# Find gaps
for agent in $AGENTS; do
echo $AGENT_DOCS | grep -qw "$agent" && echo "✅ $agent" || echo "⚠️ $agent — missing docs/docs/agents/$agent.md"
done- For each missing agent doc → STALE: scaffold a stub from the template at
docs/docs/agents/template.md.
Scaffold command:
cp docs/docs/agents/template.md docs/docs/agents/<agent-name>.md
# Then replace placeholder values: agent name, description, capabilitiesCheck 7 — Sidebar completeness
# All top-level doc section dirs
DOC_DIRS=$(ls -d docs/docs/*/ | xargs -I{} basename {})
# What's referenced in sidebars.ts
SIDEBAR_REFS=$(grep -oE "\"[a-z-]+/[a-z-]+" docs/sidebars.ts | cut -d'"' -f2 | cut -d'/' -f1 | sort -u)
for dir in $DOC_DIRS; do
echo $SIDEBAR_REFS | grep -qw "$dir" && echo "✅ $dir in sidebar" || echo "⚠️ $dir — not in sidebars.ts"
done- For missing sidebar entries → STALE: add the directory to
docs/sidebars.tsunder the appropriate category.
Check 8 — Navbar version label
grep "label.*Latest" docs/docusaurus.config.ts- If the label says
X.Y.Z (Latest)but$LATEST≠ X.Y.Z → STALE: update the label.
Step 3 — Apply fixes
Apply fixes in this order (each is independent):
- Homepage version — find-replace the old version string in
docs/src/pages/index.tsx - Docusaurus config — update
lastVersionand the version label - Version snapshot — run
npm run docusaurus -- docs:version $LATESTif missing - Missing agent stubs — scaffold from template for each uncovered agent
- Sidebar gaps — append missing dir entries to
docs/sidebars.ts - Missing release posts — delegate to
/release-docsfor each unposted tag
For checks 5 (features page tiles), always ask the user before writing — new feature tiles need copy that only the team can confirm.
Step 4 — Report
After all checks and fixes, produce a summary table:
## Docs Health Report <date>
| Check | Status | Action taken |
|-------|--------|--------------|
| Release posts | ✅ / ⚠️ | Created N posts / N missing, run /release-docs for: X.Y.Z |
| Homepage version | ✅ / ⚠️ | Updated X.Y.Z → A.B.C |
| lastVersion config | ✅ / ⚠️ | Updated |
| Version snapshot | ✅ / ⚠️ | Created versioned_docs/version-A.B.C |
| Features page | ✅ / ⚠️ | N tiles match / N new features need tiles: [list] |
| Agent docs | ✅ / ⚠️ | Scaffolded stubs for: [list] |
| Sidebar | ✅ / ⚠️ | Added entries for: [list] |
| Navbar label | ✅ / ⚠️ | Updated |If nothing is stale, say so explicitly: "All docs surfaces are up to date."
Guidelines
- Never delete existing release posts, even for yanked versions.
- Never auto-write features page tiles — copy must be human-approved.
- Agent stubs are scaffolds only — flag them clearly with a
<!-- TODO: fill in capabilities -->comment. - If
lastVersionis updated, also update the version entry label (e.g.0.4.9 (Latest)). - All file writes must follow the project's conventional commit style; suggest a commit message.
- If
git tagshows no semver tags, report "no versioned releases found" and skip version checks.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

