Auditcodexdirect Agent Skill
Send specific files to OpenAI Codex CLI for an independent audit/review
Install
one command, takes just this skill from the repositorynpx skills add https://github.com/sterlingcrispin/claude_slash_commands --skill auditcodexdirectThe instruction itself
2 sections, as written by the authorCodex Direct File Audit
Your Task
The user wants to audit specific files (not a git diff). They will provide file paths, or you should identify the relevant files from context.
- Identify the files to audit. If the user provided paths, use those. Otherwise, determine the most relevant files from the conversation context.
- Prepare a brief summary of what each file does and why it's being audited.
- Run the following command, replacing
<FILE_PATHS>with the space-separated list of files, and<FILE_SUMMARY>with a concise description of each file's purpose:
codex exec -m "gpt-5.4" -c 'model_reasoning_effort="xhigh"' -c 'service_tier="fast"' --dangerously-bypass-approvals-and-sandbox -C "$(pwd)" "You are a READ-ONLY code reviewer. Read and review the following files: <FILE_PATHS>. Review them for: bugs, security issues, performance problems, logic errors, and style concerns. Be specific about file names and line numbers. You may read other files in the repo and run tests to verify your findings. SAFETY RULES: Do NOT delete files, edit existing files, change branches, checkout, reset, revert, amend, or undo commits. Do NOT run git push, git checkout, git reset, git clean, rm, or any destructive command. You may create temporary files if needed for debugging. Your job is strictly to READ and REPORT. Do a deep audit and think from first principles. Leave no question unanswered. Here is context about the files: <FILE_SUMMARY>"
- Validate every finding before presenting it. The auditor (Codex) operates with limited context. It does not know the project's vision, strategic goals, or architectural rationale. It will often invent critical issues that are misunderstandings, or overstate the severity of things that are intentional design choices. For each finding Codex returns, you MUST:
- Check the actual source code to confirm the issue is real, not a hallucination or misread.
- Check any local strategic/planning documents (e.g.
agents.md,README.md,CLAUDE.md,current_*.md, or similar docs in the repo or in a /doc/ folderDEV_JOURNAL.mdetc) to see if the finding conflicts with the stated project intent. - Ask yourself: "Is this a real bug, or is Codex misunderstanding the context?" and "Even if real, is this meaningful or is it trivial/stylistic noise?"
- If there are findings that are not both real AND meaningful, share them with the user but clearly label them and with your reasons why.
- Present the validated findings to the user. For each one, briefly note why you believe it's legitimate. If Codex gave the all-clear, or if all findings failed validation, say so.
- Ask the user if they'd like to address any of the validated feedback.
Other skills for the same job
different authors, same section of the catalogue
Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).
Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of manual changelog writing into minutes of automated generation.
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup
Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).
React Native and Expo best practices for building performant mobile apps. Use when building React Native components, optimizing list performance, implementing animations, or working with native modules. Triggers on tasks involving React Native, Expo, mobile performance, or native platform APIs.
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.
Next.js best practices - file conventions, RSC boundaries, data patterns, async APIs, metadata, error handling, route handlers, image/font optimization, bundling
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification
How to use it
Take sterlingcrispin/auditcodexdirect from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.