skills.rest
alexeyshishin
alexeyshishinCOMMUNITY
Explore all skills by this author →
GitHub

git-pr-description

Generates a Pull Request description from the branch diff against the base branch.

4|Updated Aug 8, 2026
Search Tags:#git#diff analysis#code review#pull request#conventional commits#github cli#pr description
One-click install
npx skills add https://github.com/alexeyshishin/as-skill --skill git-pr-description-alexeyshishin
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-pr-description
Source: https://github.com/alexeyshishin/as-skill/tree/main/domains/git/skills/git-pr-description
Command: npx skills add https://github.com/alexeyshishin/as-skill --skill git-pr-description-alexeyshishin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing a good PR description is repetitive work: reviewers need to know why the change exists, what changed at a logical level, and how to verify it, but assembling that from a pile of commits by hand is tedious and often skipped. ## Core Features & Use Cases - Branch Diff Analysis: Collects all commits and the full diff of the current branch against the base branch (main/master) to build context. - Structured PR Output: Produces a title following Conventional Commits and a description with Why / What changed / How to verify / Risks sections, surfacing breaking changes explicitly. - Optional Publishing: After user confirmation, can create the PR via the GitHub CLI (gh pr create) with the prepared body. - Use Case: You finished a feature branch with six commits and need to open a PR. The skill reads the branch history, summarizes the intent and changes, and hands you a ready-to-paste description. ## Quick Start Ask the assistant to describe the PR for the current branch against main and generate the pull request description.

Frequently Asked Questions about git-pr-description

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

FAQPage Schema
How do I generate a PR description from my branch commits?▼

Run the skill on your feature branch and it compares the branch against the base branch using git log and git diff. It then produces a Conventional Commits title and a structured description with why, what changed, and how to verify sections.

How to create a GitHub pull request from the command line?▼

The skill checks for the GitHub CLI with `which gh` and, if available, runs `gh pr create --title ... --body-file ...` using the prepared description. Without gh, it gives you the text to paste into the GitHub web UI.

Does the skill push my branch or open the PR automatically?▼

No. It never pushes the branch or opens a PR without explicit confirmation. If the branch is not pushed, it shows the `git push -u origin <branch>` command and lets you decide.

What happens if the base branch cannot be detected?▼

The skill first tries `git symbolic-ref refs/remotes/origin/HEAD` to find the default branch. If that fails, it asks you directly whether the base is main or master before proceeding.

How are breaking changes handled in the PR description?▼

Breaking changes get their own Risks / breaking changes section rather than being buried in the change list. Each entry includes migration steps, or the section explicitly states there are none.

Related Skills

Explore More Software Engineering Skills→
shidax-corpshidax-corp

Commit Message

Generate conventional git commit messages and issue-based branch names.

Official
Intermediate
Zeyad-37Zeyad-37

ship-pr

Opens a pull request for a ready branch, then reviews and addresses feedback to merge.

Community
Intermediate
dwaynepartondwayneparton
1

github-pr

Creates GitHub pull requests after running tests, lint, and CI checks.

Community
Intermediate
redblacktreeredblacktree
1

source-command-ff-describe-pr

Generates pull request descriptions from repository templates using GitHub CLI.

Community
Intermediate