px-review

Run automated code reviews on git diffs for security and quality issues.

22|3|Updated Feb 22, 2026
One-click install
npx skills add https://github.com/DFilipeS/praxis --skill px-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: px-review
Source: https://github.com/DFilipeS/praxis/tree/main/praxis/skills/px-review
Command: npx skills add https://github.com/DFilipeS/praxis --skill px-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the time-consuming, inconsistent manual code review process by running focused reviewer agents in parallel and surfacing prioritized findings so teams can catch critical issues before merging.

Core Features & Use Cases

  • Reviewer discovery and selection: Automatically finds reviewer definitions and runs core reviewers for security, code quality, and simplicity, with optional additional reviewers on demand.
  • Diff-focused analysis: Reviews only the git diff (with context) to keep checks focused on changes and preserve repository privacy.
  • Parallel synthesis: Runs reviewers concurrently, aggregates results by severity (Critical, Warning, Suggestion), and preserves reviewer attribution and remediation guidance.
  • Use case: Run px-review on a feature branch to get a prioritized list of security and maintainability issues before creating a pull request.

Quick Start

Review staged changes using px-review and include the core security and code-quality reviewers.

Frequently Asked Questions about px-review

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

FAQPage Schema
How do I automate code reviews on git diffs before merging?

Automated code reviews on git diffs run focused reviewer agents in parallel to identify security, quality, and maintainability issues before merging. They analyze staged changes with contextual lines and synthesize prioritized findings without applying automatic fixes.

What is parallel automated code review and how does it work?

Parallel automated code review discovers reviewer agent definitions and executes them concurrently on git diff output. It aggregates categorized findings by severity—Critical, Warning, Suggestion—while preserving reviewer attribution and remediation guidance for the analyzed changes.

Can I run a security and code quality review on individual files or directories?

Security and code quality reviews can target individual files, directories, staged git diffs, or plan-driven review sessions. The system automatically discovers and runs core reviewers for security and simplicity, with optional additional reviewers available on demand.

Does automated code review preserve repository privacy when analyzing git diffs?

Automated code review preserves repository privacy by strictly analyzing only the git diff alongside contextual lines. This diff-focused approach keeps checks targeted on the actual changes rather than scanning the entire repository codebase.

What's the best way to review a feature branch for maintainability issues?

Reviewing a feature branch for maintainability issues is best handled by running parallel reviewer agents against the branch's git diff. This synthesizes prioritized security and maintainability findings, ensuring critical issues are caught before creating a pull request.

Does the automated review process apply automatic fixes to the codebase?

The automated review process does not apply automatic fixes to the codebase. It operates by executing reviewers in parallel on git diff output and synthesizing categorized findings with remediation guidance, leaving the actual code modifications to the developer.