github-pull-request-describe

Generate pull request titles and descriptions from committed diffs against the default branch.

1|Updated May 4, 2023
One-click install
npx skills add https://github.com/usabarashi/nix-config --skill github-pull-request-describe
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-pull-request-describe
Source: https://github.com/usabarashi/nix-config/tree/main/config/agents/skills/github-pull-request-describe
Command: npx skills add https://github.com/usabarashi/nix-config --skill github-pull-request-describe

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This tool drafts PR titles and descriptions from the committed diffs against the default branch, helping teams prepare context-rich PRs without manual summarization.

Core Features & Use Cases

  • Generate a concise PR title that reflects the changes in the diff.
  • Produce a descriptive PR body including motivation and key changes for reviewer context.
  • Use when preparing pull requests from feature branches or after a series of commits.

Quick Start

Provide the current diff and ask the assistant to generate a PR title and description.

Frequently Asked Questions about github-pull-request-describe

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

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

You can automatically generate a PR description by providing the current committed diff to the assistant. It detects the default branch, runs git fetch origin, and drafts a structured title and descriptive narrative from the changes without creating the PR.

What is the best way to draft a concise PR title from committed changes?

The best way to draft a PR title is to analyze the committed diff against the default branch. The assistant summarizes the technical changes into a concise, structured title that accurately reflects the modifications for code review preparation.

Does this PR description generator automatically detect the default branch?

Yes, the PR description generator automatically detects the default branch. It runs a git fetch origin command to ensure it compares your feature branch against the correct baseline, ensuring the generated narrative accurately reflects your committed changes.

Can I use this to prepare a pull request without actually creating it?

Yes, you can use this to prepare a pull request without creating it. The tool generates the structured title and descriptive body from the diff but does not execute the PR creation command, allowing you to review and control the final submission.

Why do I need to provide the current diff for pull request preparation?

You need to provide the current diff because the tool uses these committed changes to understand the context and motivation behind your updates. This diff against the default branch forms the foundation for generating an accurate, descriptive PR body for reviewers.