mcpField
R
review-fix-codex

review-fix-codex

github.com/willboosterTesting & quality56 installs
Repository

About review-fix-codex

A Codex-oriented skill that runs a review workflow, validates findings against accumulated facts, and guides code changes for valid issues. It is intended for code review and remediation in a project.

Key features

  1. 01Run Codex review command
  2. 02Accumulate verified facts
  3. 03Recheck findings against current code
  4. 04Fix valid findings
  5. 05Commit and push code changes

Use cases

  1. 01Reviewing a current codebase
  2. 02Validating review findings
  3. 03Fixing confirmed defects
  4. 04Tracking out-of-scope review issues

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/willbooster/agent-skills --skill review-fix-codex

After installing, type/review-fix-codexin Claude Code to confirm it loaded.

Details

From the project README

Review workflow

  1. Run the following command with a 1-hour timeout (RUN IT AS A BLOCKING, FOREGROUND TASK TO PREVENT PREMATURE TERMINATION): bunx @willbooster/agent-skills@latest review --agent codex

  2. If the command returns There is no concern., quit without modifying code. Otherwise, process the returned findings.

  3. Accumulate every returned finding as a fact inside ## Verified Facts, together with any returned ## Verified Facts. Keep only facts that still affect review: what is known, why it matters, and how it was verified.

  4. Refine accumulated facts to reduce duplication and remove stale details, then pass them through stdin with heredoc syntax:

    bunx @willbooster/agent-skills@latest review --agent codex <<'EOF'
## Verified Facts

[all accumulated facts]
EOF

  5. Determine whether each finding is still valid for the current codebase, reusing accumulated facts.

  6. Address valid findings by updating the code. For invalid findings, add explanatory comments to the code detailing why the existing implementation is necessary.

    • If there are valid review comments that are out of scope for the current PR, create new issues for them.

  7. If you made any code changes, commit and push them to the current branch.

  8. If you fixed any valid findings, return to step 4. Otherwise, quit the workflow.

Comments

Markdown supported