skills.rest
nicolaei
nicolaeiCOMMUNITY
Explore all skills by this author →
GitHub

creating-pull-requests

Draft GitHub pull request titles and bodies from user prompts.

Updated Feb 12, 2026
Search Tags:#git#github#code-review#pull-requests#conventional-commits#pr-descriptions#pr-drafting
One-click install
npx skills add https://github.com/nicolaei/claude-plugins --skill creating-pull-requests-nicolaei
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: creating-pull-requests
Source: https://github.com/nicolaei/claude-plugins/tree/main/programmer/skills/creating-pull-requests
Command: npx skills add https://github.com/nicolaei/claude-plugins --skill creating-pull-requests-nicolaei

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the drafting of GitHub pull requests with human-friendly titles and bodies, reducing back-and-forth and ensuring reviewers understand changes.

Core Features & Use Cases

  • Draft PR title with short under 70 chars and conventional commit prefixes.
  • Draft PR body with a Summary section formatted for readability.
  • Enforce rules: no lists of file changes, no "Test plan" section, no "Generated with Claude Code" footer, no Co-Authored-By trailers.
  • Example: See the provided template to maintain consistency and speed up reviews.

Quick Start

Draft a PR title and body for the user's changes following the guide above, then show the draft to the user before creating the PR.

Frequently Asked Questions about creating-pull-requests

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

FAQPage Schema
How do I write a clear GitHub pull request description for code review?▼

A clear GitHub pull request description uses a concise title under 70 characters with a conventional commit prefix and a structured Summary section formatted for readability, helping reviewers quickly grasp the code changes.

How do I draft a PR title using conventional commits?▼

Draft a PR title using conventional commits by applying standard prefixes like feat or fix, keeping the total length under 70 characters, and ensuring the title succinctly captures the intent of the code changes for reviewers.

What should I exclude from a pull request body to keep it concise?▼

Exclude lists of file changes, "Test plan" sections, "Generated with Claude Code" footers, and Co-Authored-By trailers from a pull request body to keep the description concise and focused on the summary for reviewers.

What is the best way to automate GitHub PR drafting for diverse repositories?▼

The best way to automate GitHub PR drafting is to generate a structured title and summary body from user prompts, applying consistent rules like conventional commit prefixes across typical GitHub workflows in diverse repositories.

Why does my pull request template include autogenerated footers and file lists?▼

Pull request templates include autogenerated footers and file lists when default generation tools are used, but these should be removed manually to enforce cleaner, human-friendly PR descriptions that speed up the code review process.

Related Skills

Explore More Software Engineering Skills→
bs-koobs-koo

commit

Generate Korean Git commit messages from branch types and staged changes.

Community
Advanced
tkerseytkersey
66

join

Automate GitHub PR management with CI gates and squash-merge via gh CLI.

Community
Advanced
goodstoriesworldgoodstoriesworld

git-commit-pro

Generate conventional commit messages with type, scope, and description.

Official
Intermediate
BordaBorda
24

release

Generate release notes, changelog entries, and migration guides from git history.

Community
Advanced