菜单
Use when files under docs/ may be stale. Discovers commits since the last docs update, maps changed source files to affected conceptual documentation, and brings docs/*.md back into sync.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
Use when you want to bring every drift-prone artifact in the repo back into sync. Dispatches to all individual update-* skills in the correct order, aggregates their results, and leaves a single combined PR ready to review.
Use when spotifai may have drifted from OSS_SPEC.md. Fetches the latest spec from GitHub, walks its mandates, and fixes each violation so the repository keeps conforming. Runs standalone — it does not shell out to any external validator binary.
Use when files under man/ may be stale. Discovers commits since the last manpage update, maps changed CLI definitions to affected pages, and updates man/<cmd>.md to match the current implementation.
Use when LLM prompts under prompts/ may be stale. Discovers changes since the last run and rewrites the affected prompt templates so they stay aligned with their sources of truth.
Use when README.md may be stale. Discovers commits since the last README update, identifies what user-facing surfaces changed, and brings README.md back into sync.
Use when the marketing website may be stale. Discovers commits since the last website update and refreshes source-derived content under website/ so generated pages match the current README, docs, and spec.
基于 SOC 职业分类
| name | update-docs |
| description | Use when files under docs/ may be stale. Discovers commits since the last docs update, maps changed source files to affected conceptual documentation, and brings docs/*.md back into sync. |
Governing spec sections: §11.1 (docs/ directory — the required conceptual docs tree), §21.5 (this skill is mandated because docs/ is a drift-prone artifact in every project).
The docs/ directory contains conceptual documentation for spotifai. Unlike the README (overview) or man pages (command reference), docs/ explains why and how in depth. It goes stale whenever a user-visible behavior, configuration key, or supported surface changes without a matching edit.
.agent/skills/update-docs/.last-updated contains the git commit hash from the last successful run. Empty means "never run" — fall back to the repository's initial commit.
Read the baseline:
BASELINE=$(cat .agent/skills/update-docs/.last-updated)
List commits since the baseline:
git log --oneline "$BASELINE"..HEAD
List changed files:
git diff --name-only "$BASELINE"..HEAD
Categorize using the mapping table below.
| Changed files / scope | Doc(s) to update |
|---|---|
| Public API surface | docs/getting-started.md, architecture-level docs |
| Configuration keys / env vars | docs/configuration.md |
| Error messages and exit codes | docs/troubleshooting.md |
| Deployment / install mechanics | docs/getting-started.md |
Extend this table every time you find a new source file that feeds the docs.
Read baseline from .last-updated and run git log / git diff --name-only
Read every affected docs/*.md file
Walk the mapping table and update each doc in place
Verify cross-links between docs still resolve
Verify every shell example is still syntactically valid
Run make test and the project's conformance check
Write the new baseline:
git rev-parse HEAD > .agent/skills/update-docs/.last-updated
.last-updated was rewritten.