creating-pull-requests

Generate pull request titles and descriptions from branch and commit history.

3|Updated Jan 23, 2026
One-click install
npx skills add https://github.com/lucasilverentand/skills --skill creating-pull-requests-lucasilverentand
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: creating-pull-requests
Source: https://github.com/lucasilverentand/skills/tree/main/skills/pull-requests/creating-pull-requests
Command: npx skills add https://github.com/lucasilverentand/skills --skill creating-pull-requests-lucasilverentand

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the creation of well-structured pull requests by generating conventional titles, detailed descriptions, and metadata from the current branch and commits.

Core Features & Use Cases

  • Conventional titles: Generate standardized, scope-aware PR titles.
  • Descriptive bodies: Assemble summary, changes, tests, and related issues into the PR body.
  • Issue linking & metadata: Detect linked issues and propose labels, reviewers, and assignees.
  • Use Case: On a feature branch, the skill outputs a ready-to-submit PR draft with linked issues and recommended reviewers.

Quick Start

Run the skill on a feature branch to generate a draft PR description and metadata, then review and submit via gh pr create.

Frequently Asked Questions about creating-pull-requests

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

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

This Skill generates PR descriptions from git commit history by extracting branch names and commits, then assembling conventional-commit titles, detailed bodies, and linked issues into a ready-to-submit draft.

What is a conventional-commit style pull request title?

A conventional-commit style pull request title follows a standardized, scope-aware format that categorizes the change type, such as feature or bugfix, directly in the title for better project organization and automated changelog generation.

Can I automatically link issues to a PR draft from my branch name?

Yes, you can automatically link issues by running this Skill on a branch containing issue references, which detects linked issues from branch names and commits and includes them in the assembled PR metadata.

How do I add labels, reviewers, and assignees when creating a GitHub PR from the command line?

You can add labels, reviewers, and assignees when creating a GitHub PR by using the gh pr create command, with this Skill proposing the metadata to include alongside the generated conventional title and descriptive body.

Does this PR drafting automation work with bugfix and refactor workflows?

Yes, this PR drafting automation works with bugfix and refactor workflows, applying to feature branches across GitHub repositories to extract issues and assemble appropriate PR metadata for various development tasks.

What do I need to draft a PR with this automation tool on a feature branch?

To draft a PR with this automation tool, you need a feature branch with commit history and linked issues, which the Skill processes to output a ready-to-submit PR draft for review and submission via gh pr create.