Auditcodex

sterlingcrispin/auditcodex

Send recent work to OpenAI Codex CLI for an independent audit/review

937 tokens

context cost

the whole folder, loaded on every use

files

instructions only

copies elsewhere

how many repositories repackaged it

201

stars on the repo

on the repository, not the skill itself

Install

one command, takes just this skill from the repository

npx skills add https://github.com/sterlingcrispin/claude_slash_commands --skill auditcodex

The instruction itself

3 sections, as written by the author

Codex Audit

Gather Context

Collect the recent changes for review:

Git diff (staged + unstaged): !git diff HEAD
Recent commits on this branch: !git log --oneline -10
Git status: !git status --short

Your Task

Prepare a summary of what was changed by reviewing the diff and recent commits above.

Run the following command, replacing <DIFF_SUMMARY> with a concise description of the changes, and piping the full diff via stdin:

git diff HEAD > /tmp/audit_diff.txt && 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 the file /tmp/audit_diff.txt which contains a git diff. Review it for: bugs, security issues, performance problems, logic errors, and style concerns. Be specific about file names and line numbers. You may read files 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 what changed: <DIFF_SUMMARY>"

If git diff HEAD is empty (no uncommitted changes), fall back to reviewing the last commit instead:

git diff HEAD~1 HEAD > /tmp/audit_diff.txt && 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 the file /tmp/audit_diff.txt which contains a git diff. Review it for: bugs, security issues, performance problems, logic errors, and style concerns. Be specific about file names and line numbers. You may read files 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. Here is context about what changed: <DIFF_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/ folder DEV_JOURNAL.md etc) 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.

How to use it

Copy the folder

Take sterlingcrispin/auditcodex from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

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.