create-pull-request

Create structured GitHub pull requests from commit history and issue references.

Updated Apr 3, 2026
One-click install
npx skills add https://github.com/MohitKumar9211/Lynx-Shoes --skill create-pull-request-mohitkumar9211
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-pull-request
Source: https://github.com/MohitKumar9211/Lynx-Shoes/tree/main/extensions/saoudrizwan.claude-dev-3.77.0/.agents/skills/create-pull-request
Command: npx skills add https://github.com/MohitKumar9211/Lynx-Shoes --skill create-pull-request-mohitkumar9211

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Automates and simplifies the process of creating well-structured pull requests on GitHub, ensuring adherence to project conventions and improving collaboration efficiency.

Core Features & Use Cases

  • PR Drafting: Guides users through preparing detailed and templated pull request descriptions.
  • Context Analysis: Checks commit history, branch status, and issue references to inform proper PR labeling.
  • Technical Workflow: Automates PR creation via the gh CLI, ensuring consistent formatting and metadata.

Quick Start

Provide the description for your changes and run the script to generate a pull request on GitHub.

Frequently Asked Questions about create-pull-request

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

FAQPage Schema
How do I automate GitHub pull request creation from the CLI?

Automating GitHub pull request creation involves using the gh CLI to analyze commit history, branch status, and issue tracking, ensuring consistent documentation and review processes. This workflow structures PR metadata automatically.

What's the best way to ensure consistent pull request documentation across a team?

Ensuring consistent pull request documentation requires templated PR descriptions and context analysis of commit history. This approach checks branch status and issue references to inform proper PR labeling for formal code reviews.

How does analyzing commit history improve code review workflows?

Analyzing commit history improves code review workflows by checking branch status and issue tracking to inform proper PR labeling. This ensures adherence to best practices in commit hygiene and branching workflows for collaborative projects.

Can I use the gh CLI to generate structured pull requests with issue references?

Yes, you can use the gh CLI to generate structured pull requests with issue references. The workflow automates PR creation via the CLI, ensuring consistent formatting and metadata by analyzing branch status and commit history.

Do I need any external dependencies to automate pull request creation?

No external dependencies are required to automate pull request creation beyond the standard gh CLI environment. The Skill operates independently using internal scripts and references to facilitate structured GitHub PR creation.

When should I not use automated pull request generation for code reviews?

Automated pull request generation is not suitable for collaborative software projects that do not require formal code reviews or strict adherence to branching workflows. It is designed for structured environments needing consistent documentation.