codex-review
Run OpenAI Codex's AI code review LOCALLY via the `codex` CLI BEFORE opening a PR (part of pre-PR self-review). Runs one-shot, reviewing the current branch against main, prints findings to stdout, and you resolve them before the PR is opened. Use during pre-PR self-review, alongside fx-dev:coderabbit-review.
What this skill does
# Codex Review This skill runs OpenAI Codex's AI code review **locally, one-shot**, against the current branch. Run it as part of pre-PR self-review — after `coderabbit-review`, before opening the PR — fix everything it finds, and only then open the PR. It complements (does not replace) `coderabbit-review`: CodeRabbit and Codex are independent reviewers and each catches issues the other misses. ## How to Run (one-shot, branch vs main) Codex has a dedicated non-interactive review subcommand. From the repo root, on your working branch: ```bash codex review --base main ``` This picks the current branch, diffs it against `main`, and prints the review (highest-risk findings first) to stdout — no interactive session, no edits to your tree (review is read-only). Useful variants: - **Capture to a file** for later reference (redirect stdout): `codex review --base main | tee /tmp/codex-review.md` - **Custom focus**: append a prompt, e.g. `codex review --base main "Focus on security and data-loss risks"` - **Uncommitted-only** (staged + unstaged + untracked): `codex review --uncommitted` (Run `codex review --help` for the exact flags your CLI version supports — there is no dedicated `--json`/`-o` flag, so use shell redirection to capture output.) Notes: - Prefer `--base main` so the review scope matches what the PR will contain. Use `--uncommitted` only when changes aren't committed yet. - If the workspace is externally sandboxed and Codex prompts for approvals in a non-interactive context, add `--dangerously-bypass-approvals-and-sandbox` (review is read-only, so this is safe here). Try without it first. - Requires the `codex` CLI to be installed and already authenticated. The workspace is expected to be authed; if it is not, STOP and report to the user — do NOT run `codex login` (it is interactive). ## Workflow (fix → re-run → converge) Treat Codex's findings like self-review feedback and loop until the review is clean. ### Step 1: Run the review ```bash codex review --base main ``` Use `--uncommitted` instead of `--base main` for not-yet-committed work. If the `codex` CLI is **unavailable or not authenticated**, report to the user once and skip this pass — NEVER run `codex login` (it is interactive; the workspace is expected to be authed already). ### Step 2: Resolve every actionable finding - **Fix real issues** in code and tests; make atomic commits for the fixes. - **Nitpicks** may be applied or consciously skipped — don't churn on style the project doesn't care about. There are no PR threads to resolve here (this is local); resolution = the code is fixed (or the finding is a deliberate non-issue). ### Step 3: Re-run until clean (REQUIRED) Run `codex review --base main` again after fixes. **Repeat Steps 1 → 2 until the review reports no actionable findings.** - **Cap at 4 iterations.** If Codex keeps flagging the same design decision after 4 passes, that is a human call, not more code edits — escalate to the user. ### Step 4: Open the PR only when clean A clean Codex review (alongside a clean CodeRabbit review) is the gate to PR creation in the SDLC (`fx-dev:dev` Step 4.5 → Step 5). Do not open the PR with unresolved actionable Codex findings. ## When to Use This Skill - **Pre-PR self-review:** run after `coderabbit-review` and before `pr-preparer`. Both reviewers must come back clean before the PR is opened. ## Notes - This skill is self-contained: it does not load other skills. - `codex review` reviews local changes and never modifies your working tree. - Keep findings resolved before opening the PR.
Related in AI Agents
skill-development
IncludedComprehensive meta-skill for creating, managing, validating, auditing, and distributing Claude Code skills and slash commands (unified in v2.1.3+). Provides skill templates, creation workflows, validation patterns, audit checklists, naming conventions, YAML frontmatter guidance, progressive disclosure examples, and best practices lookup. Use when creating new skills, validating existing skills, auditing skill quality, understanding skill architecture, needing skill templates, learning about YAML frontmatter requirements, progressive disclosure patterns, tool restrictions (allowed-tools), skill composition, skill naming conventions, troubleshooting skill activation issues, creating custom slash commands, configuring command frontmatter, using command arguments ($ARGUMENTS, $1, $2), bash execution in commands, file references in commands, command namespacing, plugin commands, MCP slash commands, Skill tool configuration, or deciding between skills vs slash commands. Delegates to docs-management skill for official documentation.
reprompter
IncludedTransform messy prompts into well-structured, effective prompts — single or multi-agent. Use when: "reprompt", "reprompt this", "clean up this prompt", "structure my prompt", rough text needing XML tags and best practices, "reprompter teams", "repromptception", "run with quality", "smart run", "smart agents", multi-agent tasks, audits, parallel work, anything going to agent teams. Don't use when: simple Q&A, pure chat, immediate execution-only tasks. See "Don't Use When" section for details. Outputs: Structured XML/Markdown prompt, quality score (before/after), optional team brief + per-agent sub-prompts, agent team output files. Success criteria: Single mode quality score ≥ 7/10; Repromptception per-agent prompt quality score 8+/10; all required sections present, actionable and specific.
adaptive-compaction
IncludedAdaptive add-on policy and recovery layer that decides WHEN to compact, prune, snapshot, or fork -- replacing fixed-percent auto-compaction across Claude Code, Codex, and MCP-capable hosts. Trigger on auto-compact timing or damage: "when should I compact", "is it safe to compact now or start a fresh session", "auto-compact fires too early/mid-task", "switching to an unrelated task but the window still has space", "context rot", "answers get worse the longer the session runs", "the agent forgot the plan or my decisions after it summarized", "add a layer on top that manages context without changing the agent", raising autoCompactWindow to give the policy room, or installing/tuning a cross-tool compaction policy or PreCompact hook -- even when "compaction" is never said but the problem is context-window pressure or post-summarization memory loss. Do NOT use to summarize a conversation, build RAG, write a summarization prompt (decides WHEN not HOW), or answer max-context-length trivia.
agent-skill-creator
IncludedCreate cross-platform agent skills from workflow descriptions. Activates when users ask to create an agent, automate a repetitive workflow, create a custom skill, or need advanced agent creation. Triggers on phrases like create agent for, automate workflow, create skill for, every day I have to, daily I need to, turn process into agent, need to automate, create a cross-platform skill, validate this skill, export this skill, migrate this skill. Supports single skills, multi-agent suites, transcript processing, template-based creation, interactive configuration, cross-platform export, and spec validation.
llm-wiki
IncludedUse when building or maintaining a persistent personal knowledge base (second brain) in Obsidian where an LLM incrementally ingests sources, updates entity/concept pages, maintains cross-references, and keeps a synthesis current. Triggers include "second brain", "Obsidian wiki", "personal knowledge management", "ingest this paper/article/book", "build a research wiki", "compound knowledge", "Memex", or whenever the user wants knowledge to accumulate across sessions instead of being re-derived by RAG on every query.
skill-master
IncludedAgent Skills authoring, evaluation, and optimization. Create, edit, validate, benchmark, and improve skills following the agentskills.io specification. Use when designing SKILL.md files, structuring skill folders (references, scripts, assets), ingesting external documentation into skills, running trigger evals, benchmarking skill quality, optimizing descriptions, or performing blind A/B comparisons. Keywords: agentskills.io, SKILL.md, skill authoring, eval, benchmark, trigger optimization.