create-github-pr

Create GitHub Pull Requests with branch analysis, issue search, and template application.

Updated Nov 1, 2021
One-click install
npx skills add https://github.com/elecdeer/dotfiles --skill create-github-pr-elecdeer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-github-pr
Source: https://github.com/elecdeer/dotfiles/tree/main/dot_claude/skills/create-github-pr
Command: npx skills add https://github.com/elecdeer/dotfiles --skill create-github-pr-elecdeer

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill addresses the complex process of creating a GitHub Pull Request by automating and guiding through each step, reducing manual errors and ensuring a smooth workflow.

Core Features & Use Cases

  • Comprehensive Workflow: Automates the entire process of creating a PR, including change analysis, issue search, template application, and web flow.
  • Branch Analysis: Determines the base branch and lists changed files, providing insights into modifications.
  • Issue Search: Utilizes keywords from the branch name or changed files to find related issues in the repository.
  • PR Preparation: Follows the repository's PR template structure and requirements, ensuring accurate and complete PR descriptions.
  • Impact Analysis: Determines the affected components and the nature of changes to prepare for potential issues.
  • PR Opening: Creates a PR in the browser using the gh CLI, with options for handling URL length errors.
  • Verification: Before creating a PR, verifies the remote push status to ensure all changes are accounted for.

Quick Start

Run the create-github-pr skill to start the PR creation process from the current branch.

Frequently Asked Questions about create-github-pr

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

FAQPage Schema
How do I automate GitHub pull request creation with branch analysis?

Automating GitHub pull request creation involves analyzing your current branch, searching for related issues, applying repository templates, and verifying remote push status before opening the PR. This guided workflow reduces manual errors and ensures complete change documentation.

How does PR automation find related issues for a pull request?

PR automation finds related issues by extracting keywords from your branch name and changed files, then searching the repository's issue tracker. This ensures your pull request description accurately links to existing development tasks and context.

Do I need the gh CLI installed to automate pull request workflows?

Yes, you need the gh CLI installed to automate pull request workflows. The automation uses the GitHub CLI to verify remote push status, determine base branches, and open the pull request directly in the browser, including handling URL length errors.

What is the best way to ensure a PR description follows repository templates?

The best way to ensure a PR description follows repository templates is using an automated workflow that detects and applies the repository's PR template structure. This guarantees accurate, complete descriptions that meet specific project requirements.

How to verify remote push status before opening a GitHub pull request?

To verify remote push status before opening a GitHub pull request, the automation checks your local changes against the remote repository. This verification ensures all modifications are accounted for and successfully pushed prior to PR creation.

Can PR automation determine affected components for impact analysis?

Yes, PR automation can determine affected components for impact analysis. By analyzing changed files and branch context, the workflow identifies the nature of your modifications to prepare for potential issues and streamline code review.