skills.rest
apache
apacheOFFICIAL
Explore all skills by this author →
WebsiteGitHub

review-pr

Review Apache ShardingSphere PRs and issue a definitive Merge Verdict.

20.8k|6.9k|Updated Jan 18, 2016
Search Tags:#review#root-cause#pull-request#risk-analysis#merge-verdict#shardingsphere
One-click install
npx skills add https://github.com/apache/shardingsphere --skill review-pr-apache
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review-pr
Source: https://github.com/apache/shardingsphere/tree/main/.codex/skills/review-pr
Command: npx skills add https://github.com/apache/shardingsphere --skill review-pr-apache

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Streamline the process of reviewing Apache ShardingSphere PRs by ensuring root-cause fixes are identified, side effects are evaluated, and a safe merge decision is produced.

Core Features & Use Cases

  • Root-cause-first assessment: verify that PR changes repair the underlying issue before considering merge.
  • Risk and impact analysis: evaluate design consistency, performance, compatibility, and regression surface across multiple review rounds.
  • Committer-tone feedback: generate gentle, constructional change requests when a PR is not mergeable.

Quick Start

Provide a single Merge Verdict after reviewing the PR across rounds.

Frequently Asked Questions about review-pr

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

FAQPage Schema
How do I review a ShardingSphere pull request for root-cause fixes?▼

To review a ShardingSphere PR, identify root-cause fixes and assess design integrity, performance implications, compatibility, and regression risks across multiple review rounds to produce a single definitive Merge Verdict.

What is root-cause analysis in a pull request review?▼

Root-cause analysis in a pull request review verifies that PR changes repair the underlying issue rather than masking symptoms, evaluating side effects and regression surface before producing a safe merge decision.

When should a pull request return a Not Mergeable verdict?▼

A pull request should return a Not Mergeable verdict when evidence is insufficient to prove the root-cause fix is safe, prompting a request for the minimum additional information needed from the contributor.

Does this PR review workflow evaluate performance and compatibility risks?▼

Yes, the PR review workflow evaluates performance implications and compatibility risks alongside design consistency and regression surface across multiple review rounds before generating a final Merge Verdict.

How do I generate constructive change requests for a pull request?▼

To generate constructive change requests, the review workflow produces committer-tone feedback that gently requests the minimum additional information needed when a PR is assessed as Not Mergeable.

What is the best way to assess regression risks in a ShardingSphere PR?▼

The best way to assess regression risks in a ShardingSphere PR is applying a structured review workflow that evaluates design consistency, performance, and compatibility across multiple review rounds to reach a single Merge Verdict.

Related Skills

Explore More Software Engineering Skills→
apacheapache
20.8k

analyze-issue

Analyze ShardingSphere GitHub issues to identify root causes with evidence.

Official
Advanced
kage1020kage1020

check-pr-comments

Apply pull request comment feedback as code changes and verify tests.

Community
Intermediate
NoobyGainsNoobyGains
78

quality-enforcement

Enforce code quality standards across pre-commit, pre-merge, and CI pipeline stages.

Community
Advanced
baphledbaphled
1

static-analysis

Guide static code analysis tools to detect bugs, vulnerabilities, and style violations.

Community
Intermediate