create-pr

Generate GitHub pull requests with descriptions from branch commits and related documents.

2|Updated May 27, 2026
One-click install
npx skills add https://github.com/EmergenceAI/EM-AISoftwareFactory --skill create-pr-emergenceai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-pr
Source: https://github.com/EmergenceAI/EM-AISoftwareFactory/tree/main/skills/create-pr
Command: npx skills add https://github.com/EmergenceAI/EM-AISoftwareFactory --skill create-pr-emergenceai

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, git, and includes scripts (resource) and references (resource) components.

What problem does it solve?

The create-pr Skill resolves the problem of manually creating and populating pull requests with comprehensive information, by automating the generation of pull request descriptions, analysis of branch changes, and integration of related documentation.

Core Features & Use Cases

  • PR Description Generation: Automatically creates detailed pull request descriptions using branch name analysis and documentation references.
  • Change Validation: Checks if the current branch is not the main branch, verifies PR size, and analyzes commit history.
  • Documentation Discovery: Identifies related implementation and test plans, ticket information, and cached data to provide context.
  • PR Automation: Runs tests and linting, generates PR titles and descriptions, adds labels, and creates pull requests on GitHub.
  • Use Case: When developing new features or fixing bugs, the create-pr Skill can automate the PR creation process, ensuring consistent formatting and inclusion of essential information.

Quick Start

/create-pr

Frequently Asked Questions about create-pr

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

FAQPage Schema
How do I automate GitHub pull request creation with detailed descriptions?

To automate pull request creation, you can use a Skill that analyzes branch commits and extracts related documents to generate detailed PR descriptions. It integrates documentation discovery and change validation to ensure comprehensive PR automation.

What's the best way to generate PR descriptions from branch commits?

Generating PR descriptions from branch commits is best handled by analyzing the branch name, validating changes against the main branch, and discovering related test plans. This process automatically extracts context to populate thorough PR documentation.

Do I need git and gh installed to automate PR creation workflows?

Yes, you need both git and gh installed to automate PR creation workflows. These dependencies are required to analyze branch history, validate changes, and execute the pull request creation commands directly on GitHub.

How does branch change validation work before creating a pull request?

Branch change validation works by checking if the current branch is not the main branch, verifying the PR size, and analyzing the commit history. This ensures only valid, appropriately sized changes are included in the pull request.

Can I automatically add labels and run tests when creating a GitHub PR?

Yes, you can automatically add labels and run tests when creating a GitHub PR. The automation process runs tests and linting, generates the PR title and description, adds labels, and creates the pull request seamlessly.

What should I do if my pull request documentation lacks implementation context?

If your pull request lacks implementation context, you should utilize documentation discovery features that identify related implementation plans, ticket information, and cached data. This automatically provides the necessary background for thorough PR documentation.