pre-push-review

Identify changed files since origin/main and run Codex review into a table.

2|Updated Jan 14, 2026
One-click install
npx skills add https://github.com/ignission/claude-code-ark --skill pre-push-review-ignission
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pre-push-review
Source: https://github.com/ignission/claude-code-ark/tree/main/.claude/skills/pre-push-review
Command: npx skills add https://github.com/ignission/claude-code-ark --skill pre-push-review-ignission

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams enforce code quality and security by automatically auditing changes before pushing and compiling the results into a clear report.

Core Features & Use Cases

  • Automatically identifies changed files since origin/main and triggers a deterministic review.
  • Runs Codex review on the affected files and formats results into a single table for PR discussions.
  • Useful for CI pipelines and individual contributors aiming to catch issues early before code is merged.

Quick Start

Run the pre-push-review workflow to automatically audit changes and summarize results.

Frequently Asked Questions about pre-push-review

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

FAQPage Schema
How do I automate a pre-push code review for my git changes?

You can automate a pre-push code review by identifying changes between origin/main and HEAD, then running an independent Codex review on the changed files to generate a consolidated table report for PR decisions.

What is the best way to summarize code quality and security issues before a git push?

The best way to summarize code quality and security issues is to run an automated Codex review on changed files, which collects findings into a strict tabular format suitable for PR discussions and early issue catching.

Does this pre-push review workflow integrate with existing CI pipelines?

Yes, this pre-push review workflow is designed for CI pipelines and individual contributors. It audits changes before code is merged and formats results into a single table for clear PR discussions.

How do I review only the changed files in my git branch?

To review only the changed files, the workflow automatically identifies differences between origin/main and HEAD, then triggers a focused quality review specifically on those affected files rather than the entire codebase.

Can I pass additional arguments to the Codex review process?

Yes, you can pass additional arguments to the Codex review process. The workflow executes the independent review on changed files and passes any provided arguments to customize the analysis.