creating-pr

Create GitHub pull requests from feature branches via gh pr.

121|10|Updated Mar 17, 2026
One-click install
npx skills add https://github.com/sortie-ai/sortie --skill creating-pr-sortie-ai
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: creating-pr
Source: https://github.com/sortie-ai/sortie/tree/main/.github/skills/creating-pr
Command: npx skills add https://github.com/sortie-ai/sortie --skill creating-pr-sortie-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

Automates and standardizes the creation of GitHub pull requests from feature branches, ensuring consistent metadata, branch safety checks, and a smooth review flow.

Core Features & Use Cases

  • Branch verification: prevents PR creation from protected branches and enforces pre-PR readiness.
  • Change analysis: analyzes commits and diffs to generate meaningful PR titles and descriptions.
  • PR creation: constructs reviewer-ready PRs and creates them via the GitHub CLI with proper formatting.
  • Safe workflow guidance: enforces best practices like committing changes before PR creation and avoiding PRs for unrelated work.

Quick Start

Ask the skill to create a pull request from your current branch by specifying the base and a concise description.

Frequently Asked Questions about creating-pr

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

FAQPage Schema
How do I automate GitHub pull request creation from a feature branch?▼

Automating GitHub pull request creation involves verifying your feature branch state, analyzing diffs and commits, generating titles and descriptions, and using the gh CLI to open a reviewer-ready PR with proper formatting.

Can I generate PR titles and descriptions automatically from my git commits?▼

Yes, PR titles and descriptions can be generated automatically by analyzing your branch's commit history and diffs to construct meaningful, reviewer-ready metadata without manual input.

How do I prevent creating a pull request from a protected branch?▼

You can prevent pull requests from protected branches by enforcing pre-PR readiness checks and branch verification before generating metadata, ensuring safe branching practices are applied.

Does the GitHub CLI work with automated PR creation for consistent metadata?▼

Yes, the GitHub CLI supports automated PR creation by taking generated titles and descriptions and constructing properly formatted, reviewer-ready pull requests directly from your feature branch.

What are the limitations of automating pull requests with git branch verification?▼

Limitations include the requirement to commit all changes before PR creation and the avoidance of grouping unrelated work, as the automation enforces safe workflow guidance and pre-PR readiness.

Do I need to run git commit before automating a pull request?▼

Yes, you need to run git commit before automating a pull request, as safe workflow guidance requires committing changes before PR creation to ensure branch verification and proper diff analysis.