Sponsored by

Find leads on Reddit on auto pilot

Topic: codex

8,457 skills in this topic.

create-pr Create or update GitHub PR with gh CLI. Auto-extracts ticket ID from branch name, generates title/summary from commits. Auto-detects existing PR and switches to update mode. Default: --dry-run (show command, don't execute). Use when: user asks to open/create/update a PR, says /create-pr, wants to refresh PR description after new commits, or says 'update pr', 'update PR title', 'refresh PR body'.
sd0xdev/sd0x-dev-flow 139
contract-decode EVM contract error and calldata decoder. Use when: user pastes hex revert data, calldata, function selector, or mentions custom error, execution reverted, 4byte, decode. Input contains 0x + 8+ hex chars.
sd0xdev/sd0x-dev-flow 139
codex-test-review Review test case sufficiency using Codex MCP, suggest additional edge cases. Supports review loop with context preservation.
sd0xdev/sd0x-dev-flow 139
codex-test-gen Generate unit tests for specified functions using Codex MCP
sd0xdev/sd0x-dev-flow 139
codex-setup Initialize sd0x-dev-flow infrastructure for Codex CLI and other non-Claude agents. Generates AGENTS.md, installs git hooks, copies runner scripts. Use when setting up a new project or after updating skills.
sd0xdev/sd0x-dev-flow 139
codex-security OWASP Top 10 security review using Codex MCP. Supports review loop with context preservation.
sd0xdev/sd0x-dev-flow 139
codex-review-fast Quick second-opinion using Codex MCP (diff only, no tests). Supports review loop with context preservation.
sd0xdev/sd0x-dev-flow 139
codex-review-doc Review documents using Codex MCP. Supports review loop with context preservation.
sd0xdev/sd0x-dev-flow 139
codex-review-branch Fully automated review of an entire feature branch using Codex MCP
sd0xdev/sd0x-dev-flow 139
codex-review Full second-opinion using Codex MCP (with lint:fix + build). Supports review loop with context preservation.
sd0xdev/sd0x-dev-flow 139
codex-implement Implement features via Codex MCP. Use when: writing new code from specs, implementing features, Codex-driven development. Not for: code review (use codex-code-review), architecture advice (use codex-architect). Output: implemented code + review loop.
sd0xdev/sd0x-dev-flow 139
codex-explain Explain complex code via Codex MCP. Use when: understanding complex logic, tracing data flow, onboarding to unfamiliar code. Not for: code review (use codex-code-review), exploration (use code-explore). Output: structured explanation at chosen depth.
sd0xdev/sd0x-dev-flow 139
codex-code-review Code review using Codex MCP. Use when: PR review, code audit, second opinion on changes. Not for: doc review (use doc-review), security audit (use security-review). Output: severity-grouped findings + merge gate.
sd0xdev/sd0x-dev-flow 139
codex-cli-review Code review via Codex CLI with full disk access. Use when: deep review needing full codebase read, uncommitted change review. Not for: quick diff review (use codex-code-review), doc review (use doc-review). Output: severity-grouped findings + merge gate.
sd0xdev/sd0x-dev-flow 139
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.
sd0xdev/sd0x-dev-flow 139
codex-architect Codex architecture consulting. Use when: designing features, evaluating architecture, getting second opinion on design. Not for: implementation (use codex-implement), code review (use codex-code-review). Output: architecture advice + design recommendations.
sd0xdev/sd0x-dev-flow 139
code-investigate Dual-perspective code investigation. Use when: deep code analysis needing both Claude and Codex perspectives. Not for: quick exploration (use code-explore), code review (use codex-code-review). Output: integrated findings from dual analysis.
sd0xdev/sd0x-dev-flow 139
code-explore Pure Claude code investigation. Use when: tracing execution paths, understanding architecture, diagnosing issues. Not for: dual-perspective review (use code-investigate), code review (use codex-code-review). Output: analysis report with findings.
sd0xdev/sd0x-dev-flow 139
claude-health Claude Code config health check + plugin sync. Use when: auditing .claude/ structure, checking naming, verifying hook setup, detecting plugin version drift, syncing installed assets. Not for: skill quality (use skill-health-check), code review (use codex-code-review). Output: health report + fix recommendations.
sd0xdev/sd0x-dev-flow 139
check-coverage Comprehensive assessment of Unit / Integration / E2E three-layer test coverage, identify gaps and provide actionable recommendations.
sd0xdev/sd0x-dev-flow 139
bump-version Bump package and plugin version in sync. Updates package.json, .claude-plugin/plugin.json, and install-state manifest to the same version. Use when: user says 'bump version', 'update version', '更新版本', '版本 +1', or /bump-version
sd0xdev/sd0x-dev-flow 139
bug-fix Bug fix workflow. Use when: fixing bugs, resolving issues, regression fixes. Not for: new features (use feature-dev), understanding code (use code-explore). Output: fix + regression test + review gate.
sd0xdev/sd0x-dev-flow 139
best-practices Industry best practices conformance audit with mandatory adversarial debate. Produces audit artifact: verdict (OK/WARN/FAIL) + gap roadmap + debate proof. Use when: auditing current implementation against industry standards, checking compliance with best practices, benchmarking implementation quality, verifying a codebase meets a standard. Not for: broad research/discovery without audit target (use /deep-research), code review (use /codex-review), architecture design (use /codex-architect).
sd0xdev/sd0x-dev-flow 139
ask Context-aware Q&A with auto context gathering. Use when: user has a quick question about codebase, git history, rules, docs, or skills during development. Not for: code changes (use feature-dev), code review (use codex-review-fast), deep research (use deep-research), full code trace (use code-explore). Output: structured answer with source attribution.
sd0xdev/sd0x-dev-flow 139