reviewing-code

Run codex review on the current worktree and write a structured checkpoint.

147|10|Updated Nov 17, 2025
One-click install
npx skills add https://github.com/GGPrompts/TabzChrome --skill reviewing-code-ggprompts
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reviewing-code
Source: https://github.com/GGPrompts/TabzChrome/tree/main/plugins/conductor/skills/reviewing-code
Command: npx skills add https://github.com/GGPrompts/TabzChrome --skill reviewing-code-ggprompts

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the process of code review by running codex review on the current worktree and producing a structured checkpoint with results.

Core Features & Use Cases

  • Non-interactive codex review on code changes (uncommitted, branch diffs, or specific commits).
  • Generates a structured result with a pass/fail and a list of issues, ready for automation pipelines.
  • Use Case: As part of a PR workflow, run this skill to validate changes and generate a checkpoint for the CI system.

Quick Start

Run codex review on the current worktree to generate a checkpoint: codex review --uncommitted --title "Checkpoint Review"

Frequently Asked Questions about reviewing-code

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

FAQPage Schema
How do I automate code review checkpoints in a non-interactive CI pipeline?

Automated code review checkpoints run a non-interactive codex review on your current worktree to assess changes and generate a structured pass/fail result file for your CI system.

What is a codex review checkpoint and how does it evaluate git changes?

A codex review checkpoint is a structured file containing pass/fail statuses and issue lists. It evaluates uncommitted changes, branch diffs, or specific commits non-interactively to validate code quality.

Can I run a non-interactive code review on uncommitted worktree changes?

Yes, you can execute a non-interactive code review directly on uncommitted worktree changes by applying codex review to determine the review scope and parse results into a structured checkpoint file.

How do I generate a structured pass/fail result file from a branch diff code review?

Generate a structured pass/fail result file by running a codex review on your branch diff, which parses the identified issues into a checkpoint file ready for automated software development workflows.

Does this automated code review checkpoint require manual interaction during the git workflow?

No, the automated code review checkpoint operates entirely non-interactively, allowing you to validate changes and generate results within automated software development workflows without manual intervention.