codex-review-branch
Codex Review Branch
Thin entry-point skill — routes to the parent skill for full workflow.
Parent Skill
This is the Branch variant of codex-code-review. Full workflow, prompt templates, and review logic are defined in the parent skill.
See @skills/codex-code-review/SKILL.md
Variant
| Property | Value |
|---|---|
| Scope | Full branch (all commits since base) |
| Pre-checks | None |
| Prompt template | @skills/codex-code-review/references/codex-prompt-branch.md |
Trigger
- Keywords: branch review, full branch, review branch, codex-review-branch
When NOT to Use
- Quick diff-only review (use
/codex-review-fast) - Full review with lint + build (use
/codex-review) - Document review (use
/codex-review-doc)
More from sd0xdev/sd0x-dev-flow
codex-brainstorm
Adversarial brainstorming via Claude+Codex debate. Use when: exploring solutions, feasibility analysis, exhaustive enumeration. Not for: implementation (use feature-dev), architecture only (use codex-architect). Output: Nash equilibrium consensus + action items.
7security-review
Security review via Codex MCP. Use when: OWASP Top 10 audit, dependency vulnerability check, security-sensitive changes. Not for: code review (use codex-code-review), test review (use test-review). Output: security findings + audit report.
7test-review
Test coverage review via Codex MCP. Use when: reviewing test sufficiency, identifying coverage gaps, test quality audit. Not for: generating tests (use codex-test-gen), code review (use codex-code-review). Output: coverage analysis + gap report.
7post-dev-test
Post-development test completion. Use when: checking test coverage after feature-dev, writing missing integration/e2e tests. Not for: unit test generation (use codex-test-gen), test review (use test-review). Output: test files + coverage report.
6project-audit
Project health audit with deterministic scoring. Use when: evaluating project quality, onboarding to new codebase, periodic health checks. Not for: runtime performance analysis, security-specific audits (use /codex-security). Output: 5-dimension score + actionable findings.
6request-tracking
Request tracking knowledge base. Use when: querying request status, managing document references, tracking progress. Not for: creating requests (use create-request), tech specs (use tech-spec). Output: status report + progress tracking.
6