pull-request

Generate a structured GitHub pull request body and submit it via gh CLI.

1|Updated Aug 26, 2024

Search Tags:#automation #devops #github #code-review #pull-request #pr-create #humanizer

Ready to run

npx skills add https://github.com/raghavpillai/dotfiles --skill pull-request-raghavpillai

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: pull-request
Source: https://github.com/raghavpillai/dotfiles/tree/main/.claude/skills/pull-request
Command: npx skills add https://github.com/raghavpillai/dotfiles --skill pull-request-raghavpillai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Drafting consistent, human-friendly PR descriptions and triggering PR creation on GitHub, reducing manual toil and human error.

Core Features & Use Cases

Automated PR body generation: Create a well-structured PR description with Summary, Context, and Changes.
Default-branch PR creation: Submit the PR to the repository's default branch using gh pr create.
Humanized drafting: Run a pre-write humanizer to ensure tone and clarity for teammates.

Quick Start

Draft a concise, human-friendly PR body for the latest changes and prepare a gh pr create command targeting the default branch.

Frequently Asked Questions about pull-request

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

FAQPage Schema

How do I automate creating a GitHub pull request with a structured description?▼

Automating GitHub pull request creation involves generating a structured PR body with Summary, Context, and Changes sections, then submitting it to the default branch using the GitHub CLI. This enforces consistent, human-friendly PR descriptions for code review.

What's the best way to generate human-friendly PR descriptions for code review?▼

Generating human-friendly PR descriptions requires a pre-write humanization step to ensure clear tone for teammates. This process formats repository changes into standardized Summary, Context, and Changes sections, reducing manual drafting toil and human error.

Do I need the GitHub CLI to create pull requests from the command line?▼

Yes, you need the GitHub CLI to create pull requests from the command line. The GitHub CLI handles submitting the standardized PR body to the repository's default branch, acting as the core dependency for automated PR creation.

How does a pre-write humanizer improve pull request context for teammates?▼

A pre-write humanizer improves pull request context by applying a humanization step before drafting the PR body. This ensures the tone and clarity of the Summary, Context, and Changes sections are easily understandable by teammates during code review.

Can I use automated PR body generation for any default branch on GitHub?▼

Automated PR body generation targets the repository's default branch on GitHub. It applies to software repositories requiring consistent PR descriptions, using the GitHub CLI to submit the standardized Summary, Context, and Changes sections.

Why should I use an automated pull request generator instead of manual drafting?▼

Using an automated pull request generator instead of manual drafting reduces manual toil and human error. It enforces a consistent PR body format with Summary, Context, and Changes sections, ensuring standardized review context across software repositories.