skills.rest
almazom
almazomCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

codex-review

Wrap the local Codex review tool with glm_wp fallback and per-run artifacts.

Updated Mar 25, 2026
Search Tags:#automation#backend#codex#review#local#artifact#wrapper
One-click install
npx skills add https://github.com/almazom/agents_slash_skills --skill codex-review-almazom
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: codex-review
Source: https://github.com/almazom/agents_slash_skills/tree/main/codex-review
Command: npx skills add https://github.com/almazom/agents_slash_skills --skill codex-review-almazom

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill provides a local wrapper around the Codex review tool and falls back to glm_wp with identical prompts, enabling explicit user-initiated reviews and repo-local artifacts under .codex-review/runs.

Core Features & Use Cases

  • Thin wrapper that preserves upstream review behavior while enabling auto fallback to glm_wp.
  • Writes per-run artifacts under .codex-review/runs for auditing and reproducibility.
  • Supports explicit user intent and precise selector flags like --uncommitted, --base, or --commit.

Quick Start

Run the codex-review wrapper against a target repository to perform a local Codex review.

Frequently Asked Questions about codex-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run a local code review on uncommitted changes?▼

Run a local code review on uncommitted changes by executing the wrapper with the --uncommitted selector. The tool evaluates the working directory and writes review artifacts to .codex-review/runs.

What happens if the primary Codex review tool fails during a run?▼

If the primary Codex review tool fails, the wrapper implements a dual-backend auto-fallback to glm_wp using identical prompts. Runtime warnings are issued, and the review completes while writing standard artifacts to .codex-review/runs.

How do code review artifacts ensure reproducibility for auditing?▼

Code review artifacts ensure reproducibility by writing structured outputs like report.md and run.json to the .codex-review/runs directory. These per-run files capture deterministic results for later auditing and traceability.

Can I review a specific commit hash instead of uncommitted code?▼

Yes, you can review a specific commit hash by passing the --commit selector to the wrapper. It also supports --base for branch comparisons, ensuring precise scoping for artifact-backed reviews.

Does the wrapper modify the upstream behavior of the Codex review tool?▼

No, the wrapper acts as a thin pass-through that preserves upstream Codex review behavior. It only adds auto-fallback capabilities and deterministic artifact generation without altering the core review logic.

What are the limitations of using a local wrapper for code reviews?▼

A limitation of this local wrapper is that it requires the Codex review tool and glm_wp backend to be configured in your local environment. It is designed for explicit, user-initiated workflows rather than automated continuous integration pipelines.

Related Skills

Explore More Software Engineering Skills→
alexanderopalexanderop

using-git-worktrees

Create isolated git worktrees for feature branches with safety checks.

Community
Advanced
lespacemanlespaceman
4

generate-report

Aggregate WebBench results from JSONL into a markdown report.

Community
Advanced
leboncoinleboncoin
92

run-quality-checks

Run linting, type checking, formatting, and tests for Spark UI projects.

Official
Intermediate
yun520-1yun520-1
38

code-review-assistant

Analyze code commits and pull requests for bugs, vulnerabilities, and performance issues.

Community
Advanced