write-pull-request

Generate pull request descriptions from git diff and commit history.

3|1|Updated Jun 20, 2016

Search Tags:#automation #git #diff #branch #pr #code-review #pull-request

Ready to run

npx skills add https://github.com/paulchiu/dotfiles --skill write-pull-request-paulchiu

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: write-pull-request
Source: https://github.com/paulchiu/dotfiles/tree/main/.config/opencode/skills/write-pull-request
Command: npx skills add https://github.com/paulchiu/dotfiles --skill write-pull-request-paulchiu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generates consistent pull request descriptions from the current branch changes against main, saving time for reviewers and ensuring clarity.

Core Features & Use Cases

Auto-generates a concise PR body from git diff and commit history.
If a PR template exists, fills and preserves its structure and formatting.
Supports team workflows by generating descriptive summaries for code reviews.

Quick Start

Ask it to generate a PR description for your current branch against main.

Frequently Asked Questions about write-pull-request

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 and commit history?▼

You can generate a pull request description by analyzing the git diff and commit history of your current branch against main to automatically assemble a concise, review-ready PR body.

Can I automatically fill out a PR template using my branch changes?▼

Yes, if a PR template exists in your repository, the tool fills and preserves its exact structure and formatting while populating it with details extracted from your branch changes.

What is the best way to draft PR descriptions for code reviews quickly?▼

The best way to draft PR descriptions quickly is to use an automated generator that reads your branch changes and commit history to produce a consistent summary for tracking and code review.

Do I need any specific dependencies to generate PR descriptions from branch changes?▼

No specific dependencies are required to generate PR descriptions from branch changes, as the tool relies on your existing git environment to diff the current branch against main.

Does the generated pull request body include the full commit history of the branch?▼

The generated pull request body utilizes the commit history to inform the description, ensuring the final summary accurately reflects the context and changes made on the branch.