code-review-pr-body

Generate structured pull request body drafts from git diffs.

Updated Jul 1, 2026
One-click install
npx skills add https://github.com/Jsplix/ACODIAN-ORIGIN --skill code-review-pr-body-jsplix
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review-pr-body
Source: https://github.com/Jsplix/ACODIAN-ORIGIN/tree/main/.codex/skills/code-review-pr-body
Command: npx skills add https://github.com/Jsplix/ACODIAN-ORIGIN --skill code-review-pr-body-jsplix

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually writing pull request descriptions is time-consuming, often omits critical context like breaking changes or test plans, and leads to inconsistent documentation across development teams.

Core Features & Use Cases

  • Structured PR Body Generation: Automatically creates PR drafts with standardized sections including Summary, Changes, Breaking Changes, Migration, Test Plan, and Related links.
  • Context-Aware Content: Incorporates optional design intent documents, code quality guides, and confirmed team discussion points to ensure PR descriptions are accurate and complete.
  • Use Case: Development teams submitting feature, bug fix, or refactor PRs can use this skill to eliminate manual documentation work, ensuring all required context is included for reviewers without spending time compiling change details.

Quick Start

Use the code-review-pr-body skill to generate a draft PR description for your current feature branch against the agreed base branch.

Frequently Asked Questions about code-review-pr-body

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

FAQPage Schema
How do I auto-generate a pull request description from a git diff?

To auto-generate a pull request description from a git diff, use this skill to automatically create structured PR body drafts. It analyzes your base branch git diff outputs to produce compliant descriptions with required sections like change summaries and test plans.

What is the best way to ensure breaking changes are documented in pull request bodies?

The best way to ensure breaking changes are documented in pull request bodies is to auto-generate PR descriptions from git diffs. This automatically flags breaking changes and includes migration steps within standardized PR documentation sections.

Can I include design intent documents when generating PR body drafts?

Yes, you can include design intent documents when generating PR body drafts. The skill incorporates optional review artifacts like design intent documents and confirmed team discussion points to create accurate, context-rich PR documentation.

How do I create standardized PR descriptions for feature and refactor changes?

You create standardized PR descriptions for feature and refactor changes by processing git diffs through this skill. It supports standard pull request workflows and produces compliant drafts with standardized sections including Summary, Changes, and Test Plan.

Does this PR body generation skill modify my source code?

No, this PR body generation skill does not modify your source code. It relies on base branch git diff outputs and optional review artifacts strictly to create accurate PR documentation, leaving your original source files untouched.