code-review

Merge Codex review and PAL codereview outputs into a prioritized feedback report.

3|Updated Jan 14, 2014
One-click install
npx skills add https://github.com/prateek/dotfiles --skill code-review-prateek
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/prateek/dotfiles/tree/main/.agents/skills/code-review
Command: npx skills add https://github.com/prateek/dotfiles --skill code-review-prateek

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill enables teams to generate a single, merged code-review by combining Codex review with PAL codereview against a base git ref, delivering a unified, actionable report.

Core Features & Use Cases

  • Parallel reviews: run Codex review and PAL codereview concurrently to save time.
  • Base-ref aware: compare against a specified base ref (e.g., origin/main) or evaluate pending/uncommitted changes.
  • Prioritized output: merges findings into blockers, high-signal items, and nit suggestions for actionable follow-up.

Quick Start

Provide the repository path and a base ref, then run this skill to generate a merged review.

Frequently Asked Questions about code-review

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

FAQPage Schema
How do I combine multiple code review outputs from different tools into one report?

To combine multiple code review outputs, this skill merges Codex and PAL findings against a git base ref into a single unified report categorized into blockers, high-signal items, and nit suggestions.

Can I run Codex and PAL code reviews concurrently to save time?

Yes, you can run Codex and PAL code reviews concurrently. The skill orchestrates parallel cross-tool execution to generate a merged review faster before delivering the final prioritized feedback report.

How do I generate a code review for uncommitted changes in a local git repository?

Generating a code review for uncommitted changes is supported by evaluating pending local repository modifications alongside standard base-ref comparisons like origin/main to deliver prioritized feedback.

What is the best way to prioritize code review feedback from automated git workflows?

The best way to prioritize automated code review feedback is to merge findings into blockers, high-signal items, and nit suggestions, ensuring your team receives a unified, actionable report for immediate follow-up.

Does this unified code review approach support comparisons against a specific git base ref?

Yes, unified code review supports comparisons against a specified git base ref such as origin/main, allowing you to evaluate pending changes and generate a merged review report.

What do I need to provide to start a merged code review against a base git ref?

To start a merged code review, you need to provide the repository path and a base git ref, which allows the parallel review process to run and generate a unified feedback report.