用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/sd0xdev/sd0x-dev-flow-codex --skill update-docs命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Route setup using exact migration registry [{"unit":"setup/default","routing":{"negative_boundaries":["Do not run setup; only execute deterministic repository verification.","Only assess test coverage, acceptance criteria, flakiness, and verification gaps.","Only review the current code changes for correctness and defects."],"positive_triggers":["Apply the canonical setup workflow and report its evidence.","Help me run the setup workflow for this repository.","I need the canonical setup procedure with its safety boundaries."]}},{"unit":"setup/guidance","routing":{"negative_boundaries":["Do not run setup guidance mode; only execute deterministic repository verification.","Only assess test coverage, acceptance criteria, flakiness, and verification gaps.","Only review the current code changes for correctness and defects."],"positive_triggers":["Apply the canonical setup guidance mode workflow and report its evidence.","Help me run the setup guidance mode workflow for this repository.","I need the canonical setup
Route deep-research using exact migration registry [{"unit":"deep-research/default","routing":{"negative_boundaries":["Answer a narrow repository question using one file.","Implement the recommended database migration strategy.","Trace only the internal execution path without external research."],"positive_triggers":["Compare database migration strategies using official sources, repository constraints, and real-world evidence.","Conduct deep research on this technical decision from multiple independent source types.","Research the current landscape and produce a claim registry with conflicts and confidence."]}}].
Route architecture-advice using exact migration registry [{"unit":"architecture-advice/default","routing":{"negative_boundaries":["Create the feature 3-architecture.md lifecycle document.","Implement the selected architecture in production code.","Write an implementation-ready technical specification and task breakdown."],"positive_triggers":["Compare architecture options for introducing an event bus in this codebase.","Give an independent architecture second opinion on this proposed caching design.","Recommend a component boundary for the billing integration with repository evidence."]}}].
基于 SOC 职业分类
正在显示 SKILL.md
| name | update-docs |
| description | Research current code state then update corresponding docs, ensuring docs stay in sync with code. |
| allowed-tools | Read, Write, Edit, Grep, Glob, Bash(ls:*), Bash(git:*), Bash(find:*), Bash(node:*) |
/codex-review-doc)/tech-spec or /create-request)/doc-refactor)Auto-triggered after precommit Pass, only when the change maps to a feature under docs/features/ (see @rules/auto-loop.md Doc Sync Note). Can also be invoked manually.
Key principle: can't find target → ## Gate: ⚠️ Need Human — don't guess or create new docs.
Use the shared feature context resolution algorithm (see @skills/tech-spec/references/feature-context-resolution.md):
| Confidence | Action |
|---|---|
| high/medium | Proceed with detected feature |
| low | Proceed with warning |
| null (not found) | Output ## Gate: ⚠️ Need Human — do not guess |
Key research items:
| Item | Doc Description | Current Code | Status |
|---|
Update document content based on differences:
After update:
After doc sync, compare code diff against pre-sync baseline. If new code changes exist (e.g., lint:fix modified code), return to review loop.
## Doc Update Report
| Document | Sections Updated | Status |
|----------|-----------------|--------|
## Changes Made
- <summary of each update>
## Verification
- [ ] New modules documented
- [ ] Removed modules cleaned
- [ ] Diagrams updated