Code Review
Automated code review and analysis
review-feedback-schema
by existential-birds
Schema for tracking code review outcomes to enable feedback-driven skill improvement. Use when logging review results or analyzing review quality.
exunit-code-review
by existential-birds
Reviews ExUnit test code for proper patterns, boundary mocking with Mox, and test adapter usage. Use when reviewing _test.exs files or test helper configurations.
elixir-performance-review
by existential-birds
Reviews Elixir code for performance issues including GenServer bottlenecks, memory usage, and concurrency patterns. Use when reviewing high-throughput code or investigating performance issues.
graphql-inspector-audit
by TheBushidoCollective
Use when auditing GraphQL operations for complexity metrics, depth analysis, directive usage, or query performance concerns.
next-upgrade
by vercel-labs
Upgrade Next.js to the latest version following official migration guides and codemods
uv
by OpenHands
If the project uses uv, use this skill. Use this skill to create/manage Python projects and environments with uv, add/remove dependencies, sync a project from uv.lock, and run commands in the project environment.
feature-verify
by sd0xdev
"Feature verification (READ-ONLY). Use when: verifying feature behavior, validating data integrity, confirming system state. Not for: modifying data (use feature-dev), code review (use codex-code-review). Output: verification report + confidence assessment."
feature-dev
by sd0xdev
"Feature development workflow. Use when: implementing features, writing code, running dev loop. Not for: understanding code (use code-explore), reviewing code (use codex-code-review). Output: implemented feature + tests + review gate."
codex-explain
by sd0xdev
"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."
codex-cli-review
by sd0xdev
"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."
risk-assess
by sd0xdev
"Uncommitted code risk assessment with breaking change detection, blast radius analysis, and scope metrics. Use when: evaluating PR risk, pre-commit risk check, large refactoring review. Not for: security vulnerabilities (use /codex-security), code correctness (use /codex-review-fast). Output: 3-dimension weighted score + risk level + gate."
doc-review
by sd0xdev
"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."
codex-code-review
by sd0xdev
"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."
codex-architect
by sd0xdev
"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."
claude-health
by sd0xdev
"Claude Code config health check. Use when: auditing .claude/ structure, checking naming, verifying hook setup. Not for: skill quality (use skill-health-check), code review (use codex-code-review). Output: health report + fix recommendations."
create-skill
by sd0xdev
"Create or refactor Claude Code skills. Use when: building new skills, restructuring existing skills. Not for: skill quality audit (use skill-health-check), code review (use codex-code-review). Output: skill files (SKILL.md + command + references)."
bug-fix
by sd0xdev
"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."
code-investigate
by sd0xdev
"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."
next-step
by sd0xdev
"Change-aware next step advisor. Use when: user asks what to do next, workflow progression is unclear, session just started with dirty worktree. Not for: executing the suggested command (user decides), auto-loop decisions (hooks handle that). Output: findings-based suggestions or session summary with commit seed."
create-request
by sd0xdev
"Create or update request documents. Use when: planning features, tracking requests, updating progress. Not for: tech specs (use tech-spec), code implementation (use feature-dev). Output: request document with status tracking."
project-audit
by sd0xdev
"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."
codex-implement
by sd0xdev
"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."
test-review
by sd0xdev
"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."
tech-spec
by sd0xdev
"Tech spec generation and review. Use when: designing features, writing specs, requirement analysis. Not for: implementation (use feature-dev), architecture advice (use codex-architect). Output: numbered tech spec document."