skills.rest
Olshansk
OlshanskCOMMUNITY
Explore all skills by this author →
Website𝕏@OlshanskyGitHub

cmd-pr-description

Generate concise GitHub Pull Request descriptions from code diffs.

8|Updated Jan 22, 2026
Search Tags:#automation#git#code review#github#pr#description
One-click install
npx skills add https://github.com/Olshansk/agent-skills --skill cmd-pr-description
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: cmd-pr-description
Source: https://github.com/Olshansk/agent-skills/tree/main/skills/cmd-pr-description
Command: npx skills add https://github.com/Olshansk/agent-skills --skill cmd-pr-description

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the creation of clear and concise Pull Request (PR) descriptions, saving developers time and ensuring consistent documentation.

Core Features & Use Cases

  • Automated Diff Analysis: Analyzes code changes against a base branch to identify key modifications.
  • Structured Description Generation: Outputs descriptions in a standardized Markdown format, including a summary, feature diff, and optional technical details.
  • Use Case: After pushing a set of changes for a new feature, run this Skill to generate a draft PR description that can be quickly reviewed and updated before submission.

Quick Start

Run the cmd-pr-description skill to generate a PR description for your current changes.

Frequently Asked Questions about cmd-pr-description

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

FAQPage Schema
How do I automatically generate a PR description from my Git diff?▼

To automatically generate a PR description from your Git diff, this Skill analyzes your code changes against a specified base branch, extracts key modifications, and summarizes them into a standardized Markdown file for GitHub.

Can I use the GitHub CLI to create pull request descriptions from code changes?▼

Yes, you can use the GitHub CLI alongside this Skill to generate and update pull request descriptions. It detects branch changes and formats the summarized code differences directly for your GitHub PRs.

What is the best way to write concise GitHub PR descriptions for new features?▼

The best way to write concise GitHub PR descriptions for new features is to analyze the code differences against a base branch, extract key changes, and output a structured Markdown summary for quick review.

Do I need to specify a base branch when generating pull request documentation?▼

Yes, you need to specify a base branch when generating pull request documentation. The Skill compares your current code changes against this base branch to accurately extract and summarize the key feature modifications.

What format does the automated PR description output use for code review?▼

The automated PR description output uses a standardized Markdown format for code review. This structured output includes a summary of changes, a feature diff, and optional technical details to ensure consistent documentation.

Related Skills

Explore More Software Engineering Skills→
JohnWebb4JohnWebb4

dev-workflow-write-pr

Automates GitHub pull-request creation by analyzing diffs and generating descriptions from templates.

Community
Advanced
brainbrewlabsbrainbrewlabs
7

git

Coordinates Git commit, push, and PR actions via git-manager modes.

Official
Intermediate
barikata1984barikata1984

quality-review

Automates git-based code quality reviews for commits and pull requests.

Community
Intermediate
Berries-WangBerries-Wang

summarize-changes

Summarize uncommitted Git changes and identify potential risks.

Community
Basic