onex-pr-review

Analyze pull request changes, classify issues by severity, and generate a merge readiness report.

2|2|Updated Mar 28, 2026
One-click install
npx skills add https://github.com/Julian0444/omnicursor --skill onex-pr-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: onex-pr-review
Source: https://github.com/Julian0444/omnicursor/tree/main/.cursor/skills/onex-pr-review
Command: npx skills add https://github.com/Julian0444/omnicursor --skill onex-pr-review

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires requests, github3.py, and includes scripts (resource) components.

What problem does it solve?

This Skill streamlines the process of reviewing pull requests, ensuring that all critical issues are identified and addressed before merging, thereby maintaining code quality and consistency.

Core Features & Use Cases

  • Structured Assessment: Provides a structured approach to review all changes in a pull request, categorizing issues by priority.
  • Merge Readiness Verdict: Assesses and communicates the readiness of a pull request for merging, ensuring code quality.
  • Use Case: When reviewing a pull request, use this Skill to automatically generate a comprehensive review report, making it easier to identify and prioritize fixes.

Quick Start

To initiate a review for a pull request, run the 'onex-pr-review' command followed by the PR number or branch information.

Frequently Asked Questions about onex-pr-review

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

FAQPage Schema
How do I generate a merge readiness report for a GitHub pull request?

To generate a merge readiness report for a GitHub pull request, run the review command followed by the PR number or branch information. The tool systematically analyzes all changes and classifies identified issues by severity to produce the final report.

Can I review local diffs without pushing to GitHub?

Yes, you can review local diffs without pushing to GitHub. The tool supports analyzing both GitHub pull requests and local diffs, systematically categorizing any identified issues by priority before generating the final assessment.

Do I need the gh CLI installed to assess pull request merge readiness?

Yes, you need the gh CLI installed for optimal performance when assessing pull request merge readiness. The tool also requires a Python environment alongside the gh CLI to systematically analyze changes and classify issues.

How does classifying issues by severity help with code review?

Classifying issues by severity during a code review helps by structuring the feedback based on priority. This ensures critical problems are identified and addressed before merging, maintaining code quality and consistency across the project.

What's the best way to systematically analyze all changes in a pull request?

The best way to systematically analyze all changes in a pull request is to use a structured code review tool. This tool evaluates all modifications, categorizes issues by severity, and generates a comprehensive merge readiness verdict.