pull-request

Automate pull request creation and updates across GitHub, GitLab, and Gerrit.

16|1|Updated Jun 26, 2025

Search Tags:#git #workflow #development #code review #documentation #pull request #github #gitlab

One-click install

npx skills add https://github.com/bendrucker/claude --skill pull-request

Or copy as Structured Prompt for Agent▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill standardizes pull request creation, ensuring clear, concise, and informative PRs that accelerate code reviews and improve collaboration.

Core Features & Use Cases

Structured PRs: Guides on crafting titles and bodies with specific sections (Issue, Changes, Testing, References).
Contextual Information: Uses git status, git diff, and git log to gather relevant context for the PR description.
Workflow Automation: Provides a step-by-step workflow for branching, staging, committing, and pushing changes before PR creation.
Use Case: When you've finished a coding task, this Skill helps you generate a comprehensive pull request description that clearly communicates your changes, making it easy for reviewers to understand and approve.

Quick Start

Example PR title:

fix: add timeout to request

Example PR body structure:

Start with 1-3 sentences summarizing the change.

## Changes

- Adds POST /users endpoint to create users

- Refactors UserService to use dependency injection.

## Testing

- Added unit tests for new endpoint.

- Manual steps:

### Verify user creation

1. Call POST /users with valid payload.

2. Check database for new user.

Frequently Asked Questions about pull-request

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

FAQPage Schema

How do I write pull request titles and bodies that follow best practices?▼

Pull request titles should use imperative mood, lowercase (except proper nouns), and stay under 50 characters. Bodies should include structured sections: a 1–3 sentence summary, then Changes, Testing, and References sections with bullet points. This format makes reviews faster and clearer for collaborators.

Can I automate pull request creation across GitHub, GitLab, and Gerrit?▼

Yes. This Skill standardizes PR, MR, and CR creation across GitHub, GitLab, and Gerrit by enforcing consistent title conventions, body structure, and contextual information gathering from git status, git diff, and git log output.

What should I include in a pull request body?▼

A PR body should start with a brief summary of changes, then include Changes (what was added or refactored), Testing (unit tests and manual verification steps), and References (linked issues). Wrap code identifiers in backticks for clarity.

How do I gather context for my pull request description?▼

Use git commands to extract context: git status shows staged files, git diff displays actual changes, and git log reveals commit history. This Skill integrates these outputs with context.md guidance to generate comprehensive, accurate PR descriptions.

Does this Skill enforce character limits on pull request titles?▼

Yes. PR titles are limited to 50 characters maximum, with a soft guideline of 100 characters for the entire subject line. This keeps titles scannable in logs and review interfaces while staying within platform conventions.

What's the best workflow for creating pull requests with proper formatting?▼

Branch, stage changes, commit with clear messages, push to remote, then use this Skill to generate a formatted PR that includes structured sections and contextual information. The step-by-step workflow ensures consistency and clarity for code reviewers.