From sd0x-dev-flow
Reviews Markdown documents and tech specs via Codex MCP in 5 dimensions: architecture design, performance, security, documentation quality, code consistency. Outputs rating table and merge gate for audits.
npx claudepluginhub sd0xdev/sd0x-dev-flow --plugin sd0x-dev-flowThis skill is limited to using the following tools:
- Keywords: review doc, document review, tech spec review, review-spec, doc-refactor, streamline doc
Reviews technical documentation like READMEs, API docs, and guides for novice users, rating clarity, completeness, actionability, structure, and suggesting concrete fixes.
Assesses documentation quality across readability, consistency, audience fit, and prose clarity. Produces scored reviews with actionable findings before releases or doc reviews.
Reviews documentation quality using checklists for voice, tone, structure, completeness, clarity, and technical accuracy. For draft reviews, audits, and style compliance checks.
Share bugs, ideas, or general feedback.
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