create-pr

Create GitHub pull requests via gh CLI with Jira ticket detection.

2|Updated Aug 18, 2025
One-click install
npx skills add https://github.com/ESO-Toolkit/eso-toolkit --skill create-pr-eso-toolkit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-pr
Source: https://github.com/ESO-Toolkit/eso-toolkit/tree/main/.github/skills/create-pr
Command: npx skills add https://github.com/ESO-Toolkit/eso-toolkit --skill create-pr-eso-toolkit

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill automates the creation of GitHub pull requests, ensuring consistency, capturing necessary details like screenshots for UI changes, and adhering to best practices for branch management and Jira integration.

Core Features & Use Cases

  • Automated PR Creation: Uses gh CLI to create pull requests from your current branch.
  • Jira Integration: Automatically detects and links Jira ticket numbers from branch names.
  • UI Change Screenshot Capture: Detects UI changes and guides you through capturing and embedding screenshots in the PR description.
  • Best Practice Enforcement: Enforces checks for branch status, pre-commit validation, and correct base branch usage.
  • Use Case: After finishing a feature on a branch like ESO-1234/add-user-profile, run this Skill to create a PR, automatically linking it to the Jira ticket, including screenshots if UI was modified, and ensuring the correct base branch is targeted.

Quick Start

Run the create-pr skill to generate a pull request for your current branch, automatically including relevant details and screenshots if UI changes were made.

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 Jira ticket links from branch names?

You can automate GitHub pull request creation by using the GitHub CLI to detect Jira ticket numbers embedded in your branch names and automatically link them in the PR description. This ensures consistent Jira integration without manual lookup.

How do I add screenshots to a pull request description automatically for UI changes?

To add screenshots to a pull request for UI changes, this automation detects UI modifications and guides you through capturing and embedding screenshots directly into the PR description. This ensures visual changes are properly documented.

Does this PR automation enforce pre-commit validation and correct base branch targeting?

Yes, this PR automation enforces pre-commit validation and ensures correct base branch targeting, particularly for stacked branches. It checks branch status before creation to maintain codebase integrity and prevent invalid merges.

What is the best way to create a GitHub PR from a stacked branch without targeting the wrong base?

The best way to create a GitHub PR from a stacked branch is to use automation that automatically identifies and targets the correct base branch. This prevents accidental merges into main and preserves the intended review hierarchy.

Do I need the GitHub CLI installed to automate pull request creation and branch checks?

Yes, you need the GitHub CLI installed to automate pull request creation and execute branch checks. The automation relies directly on the GitHub CLI to interact with your repository, validate status, and open the pull request.

Why does my automated pull request require pre-commit validation before opening?

Automated pull requests require pre-commit validation to ensure code quality and prevent broken builds from entering the review pipeline. Enforcing these checks guarantees that only compliant branches are published as pull requests.