pr

Name: pr
Availability: InStock
Author: xiongxianfei

Summarize diffs and validation evidence into a reviewer-ready PR body.

3|Updated Apr 19, 2026

Search Tags:#pr #code-review #pull-request #diff-summary #verification-evidence #reviewer-notes

Ready to run

npx skills add https://github.com/xiongxianfei/rigorloop --skill pr-xiongxianfei

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: pr
Source: https://github.com/xiongxianfei/rigorloop/tree/main/.codex/skills/pr
Command: npx skills add https://github.com/xiongxianfei/rigorloop --skill pr-xiongxianfei

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prepare PRs that are ready for human review by summarizing the actual diff, validation evidence, and reviewer notes.

Core Features & Use Cases

Summarizes diffs and validation evidence
Aligns changes with the spec and architecture docs
Generates a reviewer-ready PR body and notes

Quick Start

Summarize the current diff and validation evidence, then draft a PR body with reviewer notes.

Frequently Asked Questions about pr

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

FAQPage Schema

How do I prepare a pull request with diff summaries and verification evidence for code review?▼

It generates a reviewer-ready PR body and notes by summarizing the actual diff and validation evidence, aligning changes with the spec and architecture ADRs for traceable decisions.

What do I need to generate reviewer notes and a structured PR body from my feature branch?▼

You need access to the actual diff, test results, architecture ADRs, and the proposed plan to generate a structured PR body and reviewer notes for explicit review gates.

Can I use automated PR readiness checks for feature branches that are near-ready across different software projects?▼

Yes, automated PR readiness applies to ready or near-ready feature branches across software projects requiring explicit review gates and traceable decisions.

How does diff summarization align code changes with architecture docs and proposed plans?▼

Diff summarization aligns code changes by mapping the actual diff against architecture ADRs and the proposed plan, ensuring the PR body reflects traceable decisions and spec compliance.

What is the best way to summarize validation evidence for a reviewer-ready pull request?▼

The best way to summarize validation evidence is to extract test results and map them to the diff, generating structured reviewer notes that provide traceable decisions for human reviewers.