菜单
Use when code changes may require documentation updates or stale documentation review
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use when reviewing a spec or task graph for completeness before implementation
Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, logging in, or automating browser actions
Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, logging in, or automating browser actions
Use when decomposing a spec, design, or feature description into a task dependency graph with self-evaluating acceptance criteria
Use when doing creative product, feature, component, functionality, or behavior design work
Use when infrastructure or features are built but before declaring done -- verifies work is wired into the system and actively used
| name | review-docs |
| description | Use when code changes may require documentation updates or stale documentation review |
After code changes, verify that documentation still matches reality. Stale docs are worse than no docs.
Review the diff or recent commits to understand what changed — new features, renamed APIs, changed behavior, removed functionality.
Search for documentation that references the changed code:
rg "changed_thing" docs/ README.md *.md
Include docstrings, inline comments, and config files — not just standalone docs.
Check each affected document against these lenses:
## Doc Review: [scope]
### Summary
X docs checked | Y issues (Z critical, W high)
### CRITICAL
- **[Issue]** `file:line` — [what's wrong] → [fix]
### HIGH
- **[Issue]** `file:line` — [what's wrong] → [fix]
### MEDIUM / LOW
- ...
### Missing Coverage
- New feature X has no documentation
### Clean
- `docs/setup.md` — still accurate
Review phase is read-only. Present findings first, then fix only after user says go.