skills/doc-review/SKILL.md
Document review via Codex MCP. Use when: reviewing .md docs, tech spec audit, document quality check. Not for: code review (use codex-code-review), test review (use test-review). Output: 5-dimension rating table + gate.
npx skillsauth add sd0xdev/sd0x-dev-flow doc-reviewInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
codex-code-review)test-review)| Command | Description | Use Case |
| ------------------- | ---------------------- | ----------------- |
| /codex-review-doc | Codex reviews .md docs | Document changes |
| /review-spec | Review tech spec | Spec confirmation |
| /doc-refactor | Streamline documents | Doc too long |
| /update-docs | Research & update docs | After code change |
/codex-review-docDetermine target → Read content → Codex review (5 dimensions) → Rating table + Gate → Loop if Needs revision
| Condition | Action |
|-----------|--------|
| Path specified | Use that path directly |
| No path | Auto-detect: git modified .md → staged .md → new .md |
| Multiple files | List and ask user which to review |
Read target file, save as FILE_CONTENT.
First review: mcp__codex__codex with doc review prompt. See references/codex-prompt-doc.md.
Config: sandbox: 'read-only', approval-policy: 'never'
Save the returned threadId.
Loop review: mcp__codex__codex-reply with re-review template. See references/review-loop-doc.md.
Organize results into rating table + severity-grouped findings + gate.
| Dimension | Checks | | ------------------- | ------ | | Architecture Design | System boundaries, responsibilities, dependencies, extensibility | | Performance | Bottlenecks, concurrency, caching, resource usage | | Security | Data leakage, access control, input validation, error handling | | Documentation Quality | Structure, completeness, accuracy, examples, docs-writing standards | | Code Consistency | Pseudocode matches codebase, referenced files exist, technical accuracy |
⚠️ @CLAUDE.md auto-loop: fix → re-review → ... → ✅ PASS ⚠️
⛔ Needs revision → fix 🔴 items → /codex-review-doc --continue <threadId> → repeat until ✅ Mergeable.
Max 3 rounds. Still failing → report blocker.
| Change Type | Must Execute |
| ----------- | ------------------------------------- |
| .md docs | /codex-review-doc or /review-spec |
| Tech spec | /review-spec |
| README | /codex-review-doc |
references/codex-prompt-doc.mdreferences/review-loop-doc.mdInput: /codex-review-doc docs/features/xxx/tech-spec.md
Action: Read file → Codex doc prompt → Rating table + Findings + Gate
Input: /codex-review-doc
Action: Auto-detect changed .md → Codex doc prompt → Rating table + Gate
Input: Review this tech spec for me
Action: /review-spec → Check completeness/feasibility/risks → Output Gate
Input: This document is too long, streamline it
Action: /doc-refactor → Tabularize + Mermaid → Output comparison
documentation
Rewrite the previous reply in Traditional Chinese
development
Monitor GitHub Actions CI runs until completion. Use when: watching CI after push, checking build status, monitoring PR checks, waiting for CI completion, user says 'watch CI', 'check CI', 'CI status', 'monitor build', or /watch-ci. Not for: pushing code (use push-ci), creating PRs (use create-pr). Output: per-run verdict (pass/fail/timeout).
development
Verification loop — lint -> typecheck -> unit -> integration -> e2e
development
Research current code state then update corresponding docs, ensuring docs stay in sync with code.