skills.rest
paulovictor237
paulovictor237COMMUNITY
Explore all skills by this author →
GitHub

pr-description

Generate a non-technical Git pull request description from diffs and commits.

Updated Aug 27, 2026
Search Tags:#automation#git#template#github#pull-request#pr-description
One-click install
npx skills add https://github.com/paulovictor237/PeveAgent --skill pr-description-paulovictor237
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pr-description
Source: https://github.com/paulovictor237/PeveAgent/tree/main/.agents/skills/pr-description
Command: npx skills add https://github.com/paulovictor237/PeveAgent --skill pr-description-paulovictor237

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Developers often spend time writing non‑technical, business‑focused pull request descriptions and manually determining the correct base branch, leading to inconsistent documentation and delayed reviews.

Core Features & Use Cases

  • Reads the repository’s pull request template (or a default template) and fills each section with concise, business‑oriented text.
  • Detects the most likely base branch using a helper script and confirms the choice with the user.
  • Gathers diff, commit list, and modified files, optionally enriches the description with Jira ticket information, and compiles everything into the PR body.
  • Offers a single command to create the pull request via the GitHub CLI, returning the PR URL.

Quick Start

Ask the skill to generate a PR description and open the pull request for the current branch.

Frequently Asked Questions about pr-description

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

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

To generate a pull request description, the skill extracts diffs, commit lists, and modified files from your current feature branch. It then assembles this data into a clear, non-technical PR body by filling out the repository's pull request template.

Can I create a GitHub pull request directly from the command line using a template?▼

You can create a GitHub pull request directly using the GitHub CLI. The skill compiles the generated description and optionally executes a single command to open the PR, returning the resulting PR URL for immediate access.

How do I determine the correct base branch when opening a pull request?▼

To determine the correct base branch, a helper script automatically detects the most likely target. The skill then confirms this detected base branch choice with you before proceeding to assemble and create the pull request.

How do I add Jira ticket details to a pull request body automatically?▼

Adding Jira ticket details to a pull request body is handled by optionally enriching the compiled description. The skill gathers branch commits and diffs, then integrates the specified Jira ticket information into the final PR template output.

What is the best way to write non-technical PR descriptions for business stakeholders?▼

Writing non-technical PR descriptions for business stakeholders is done by extracting code diffs and transforming them into concise, business-oriented text. This approach replaces manual writing to ensure consistent documentation and accelerate review cycles.

Related Skills

Explore More Software Engineering Skills→
jayteealaojayteealao

review:quick

Automate structured code reviews by analyzing git diffs with five checklists.

Community
Basic
MJ-AgentLabMJ-AgentLab

check-merge

Check Pull Request merge readiness via GitHub CLI for conflicts, CI, and approvals.

Official
Advanced
CodySwannGTCodySwannGT
3

jira-sync

Synchronize plan progress and development milestones to linked JIRA tickets.

Community
Intermediate
dakotahpdakotahp

pr-description

Generate pull request titles and descriptions from git branch commits and diffs.

Community
Intermediate