skills.rest
gaebalai
gaebalaiCOMMUNITY
Explore all skills by this author →
Website𝕏@gaebalaiGitHub

pr-write

Generates a structured PR description and review checklist from git changes.

2|Updated Feb 25, 2026
Search Tags:#git#developer tools#code review#documentation#pull request#pr
One-click install
npx skills add https://github.com/gaebalai/claude-code-kit-ko --skill pr-write
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pr-write
Source: https://github.com/gaebalai/claude-code-kit-ko/tree/main/.claude/skills/pr-write
Command: npx skills add https://github.com/gaebalai/claude-code-kit-ko --skill pr-write

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the creation of comprehensive Pull Request (PR) descriptions and review checklists, ensuring clarity and efficiency in the code review process.

Core Features & Use Cases

  • Automated PR Description Generation: Creates a structured PR description based on code changes.
  • Review Checklist Creation: Generates a checklist to guide reviewers on key aspects like logic, security, and performance.
  • Use Case: After making several code changes for a new feature, use this Skill to automatically generate a PR description that summarizes the changes, explains the implementation, and provides a checklist for reviewers to ensure quality.

Quick Start

Generate a PR description for the current code changes.

Frequently Asked Questions about pr-write

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

FAQPage Schema
How do I generate a pull request description from git diff automatically?▼

A review checklist for pull requests is created by analyzing git changes and generating a detailed checklist covering logic, security, performance, and compatibility. This ensures reviewers can systematically verify key quality aspects and the impact scope of the submitted code.

Can I categorize code changes for documentation using git status and log?▼

Yes, you can categorize code changes for documentation by analyzing git status and log data. The Skill processes your current branch updates to classify modifications into distinct categories like feature additions, bug fixes, refactoring, tests, configuration, or documentation automatically.

What is the best way to summarize a git branch's changes for code review?▼

The best way to summarize git branch changes for code review is to generate a structured PR description and review checklist. This approach provides a concise title, a summary of modifications, categorized changes, and a checklist covering logic, security, performance, and compatibility.

Does generating a PR description require specific git branch configurations?▼

Generating a PR description requires a standard git environment with committed branch changes. The Skill relies on analyzing standard git diff, log, and status outputs from your current working branch, requiring no additional dependencies or specialized configuration setup.

Related Skills

Explore More Software Engineering Skills→
jk278jk278

git-analyzer

Analyze git repositories to summarize commit history and file changes.

Community
Intermediate
chiptoe-svgchiptoe-svg

qodo-pr-resolver

Fetch, deduplicate, and resolve Qodo review comments across GitHub, GitLab, Bitbucket, and Azure DevOps.

Community
Advanced
lexmountlexmount
19

pr-unresolved-solutions

Generate structured solution proposals for unresolved pull request review threads.

Official
Advanced
aaronlordaaronlord
1

review

Automate multi-axis code review across standards, security, performance, and documentation.

Community
Advanced