Verified:GitHub

pull-merge-request-creation

Generate GitHub and GitLab pull request descriptions from branch diffs and templates.

9|1|Updated Jul 9, 2025

Search Tags:#github #gitlab #generate #code-review #pull-request #merge-request

One-click install

npx skills add https://github.com/KemingHe/common-devx --skill pull-merge-request-creation

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: pull-merge-request-creation
Source: https://github.com/KemingHe/common-devx/tree/main/.agents/skills/pull-merge-request-creation
Command: npx skills add https://github.com/KemingHe/common-devx --skill pull-merge-request-creation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generating concise, review-ready pull request or merge request descriptions that follow repository conventions and communicate changes, impact, and testing guidance without manual drafting.

Core Features & Use Cases

Platform-aware template resolution: Automatically detect GitHub or GitLab and locate repository PR or MR templates for consistent output.
Repository-aware summaries: Use read-only git reconnaissance and branch diffs to summarize changes, propose conventional commit-style titles, and link related issues.
Reviewer-ready guidance: Structure descriptions with impact, testing notes, dependencies, and rollback considerations so reviewers can act quickly.
Use case: Create a PR description for a feature branch that explains scope, affected modules, testing performed, and which issues are closed.

Quick Start

Create a PR description for the current branch that summarizes what changed, why it matters, how to test it, and which issues it closes.

Frequently Asked Questions about pull-merge-request-creation

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

FAQPage Schema

How do I generate a pull request description from a branch diff?▼

To generate a pull request description, the Skill uses read-only git reconnaissance and branch diffs to summarize code changes, propose conventional commit-style titles, and link related issues automatically.

Can I use this to create merge request descriptions for GitLab repositories?▼

Yes, you can create merge request descriptions for GitLab repositories. The Skill provides platform-aware template resolution to automatically detect GitHub or GitLab and locate the correct PR or MR templates.

What should a reviewer-ready pull request description include?▼

A reviewer-ready pull request description should include structured sections for impact, testing notes, dependencies, and rollback considerations so reviewers can act quickly and understand the scope of code changes.

How do repository templates affect PR generation?▼

Repository templates guide PR generation by enforcing repository template hygiene constraints. The Skill resolves these platform-specific templates to ensure the output follows your repository's established conventions and structure.

Does this Skill write code or only summarize existing branch changes?▼

The Skill only summarizes existing branch changes. It performs read-only git reconnaissance to analyze diffs and communicate code changes, impact, and review guidance without modifying your actual source code.

What is the best way to structure a PR description for feature branches?▼

The best way to structure a PR description for feature branches is to explain the scope, affected modules, testing performed, and which issues are closed, using conventional commit-style titles for clear communication.