菜单
Review docs for drift, missing updates, and terminology changes. Use when code changes should be reflected in documentation.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Create and update AGENTS.md project rules. Use when authoring or amending the cross-tool conventions agents must follow.
Write forward-looking startup instructions for the next session, then reset context to save costs. Use when the context is getting long or before switching focus.
Run pre-release checks, pick the version bump, and cut the release. Use when ready to tag and release.
Create and maintain a specification that states what to build, not how. Use when writing a spec, editing requirements, or defining acceptance criteria.
Run all review dimensions against a diff or a path. Use when reviewing a feature branch before merge, reviewing someone else's PR, or auditing a file path.
Create or update project documentation. Use when creating architecture docs, runtime docs, reference docs, or design documents that explain what the system does.
| name | doc-review |
| description | Review docs for drift, missing updates, and terminology changes. Use when code changes should be reflected in documentation. |
Review the docs the diff affects for drift — terms, contracts, and behavior the change made stale.
Report only drift caused or exposed by the diff. Pre-existing doc debt untouched by the change is out of scope unless the change makes it actively wrong.
Apply these only to lines the change adds or modifies — never flag untouched text.
Read the diff, then the affected doc files. For changes touching many docs, fan out fast-tier readers — one per doc — to surface drift candidates. Verify each before reporting.
For each finding: label (Critical / Fix / Consider / Nit — see review), affected file, what drifted or is missing, fix direction.
docs/config.md still says maxRetries defaults to 3; this diff changes it to 5 in src/client.ts.Group as Canonical updates needed | Optional cleanup (max 3, each tied to a file the diff touched; omit if empty). If nothing drifted, say "No doc findings".
review for cross-dimension merge decisionspr for change summaries and issue linkage