code-review-pr-body

Generate structured pull request body drafts from git diff outputs.

Updated Jun 5, 2026

Search Tags:#automation #workflow #documentation #pr #generate #pull-request #git-diff

Ready to run

npx skills add https://github.com/KangJiSseok/ACODIAN --skill code-review-pr-body

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: code-review-pr-body
Source: https://github.com/KangJiSseok/ACODIAN/tree/main/.codex/skills/code-review-pr-body
Command: npx skills add https://github.com/KangJiSseok/ACODIAN --skill code-review-pr-body

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

PR 본문 작성의 반복 작업을 줄이고, git diff와 산출물 문서를 바탕으로 일관된 PR 초안을 자동으로 생성합니다.

Core Features & Use Cases

변경된 파일을 모듈/영역 단위로 분류하고 PR 본문 구조에 맞춰 Summary, Changes, Breaking Changes, Test Plan를 자동으로 구성합니다.
design-intent, code-quality-artifacts 등의 관련 자료가 있을 경우 이를 PR 본문에 반영합니다.
Use Case: feature branch PR 생성 직전에 본문이 필요할 때, 자동 초안으로 리뷰 시간을 단축합니다.

Quick Start

git diff를 기준으로 PR 본문 초안을 자동으로 작성하려면 '$code-review-pr-body'를 명시 호출한다.

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 automatically generate a pull request body from a git diff?▼

To generate a pull request body from a git diff, use an automation tool that parses diff outputs and categorizes file changes into structured sections like Summary, Changes, Breaking Changes, and Test Plan. This provides a consistent PR draft without manual writing.

What is the best way to structure a PR draft for a feature branch?▼

The best way to structure a PR draft is by categorizing changed files into module or area units, then mapping them into Summary, Changes, Breaking Changes, and Test Plan sections. This ensures reviewers can quickly understand the scope and impact of the feature branch.

Can I include design intent or code quality artifacts in my generated PR body?▼

Yes, you can include design intent and code quality artifacts in a generated PR body. The generation process relies on git diff outputs and accepts optional PR artifacts, reflecting these related documents directly within the structured draft sections.

Does generating a PR draft from git diffs modify my source code?▼

Generating a PR draft from git diffs does not modify source code. The process strictly reads git diff outputs and related artifacts to produce a text draft, leaving your actual repository files and source code completely untouched.

When do I need to automate pull request body generation?▼

You need to automate pull request body generation right before creating a pull request for a feature branch. Automating this repetitive task produces a consistent draft immediately, which significantly shortens the time reviewers spend understanding the changes.

What should a pull request body include for faster code review?▼

A pull request body for faster code review should include a high-level summary, detailed changes by module, explicit breaking changes, and a defined test plan. Organizing file diffs into these specific sections helps reviewers quickly locate and assess critical updates.