pr-create

Create pull requests from local commits via GitHub CLI.

1|1|Updated Jun 11, 2024
One-click install
npx skills add https://github.com/ag-grid/ag-shared --skill pr-create-ag-grid
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-create
Source: https://github.com/ag-grid/ag-shared/tree/main/prompts/skills/pr-create
Command: npx skills add https://github.com/ag-grid/ag-shared --skill pr-create-ag-grid

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates creating a pull request from current commits and local changes, handling branch naming, base branch selection, and PR submission.

Core Features & Use Cases

  • Assess repository state (status, log, current branch, remotes) to decide actions.
  • Determine base branch automatically or based on user preference; create a topic branch if needed.
  • Commit changes with conventional messages, push to origin, and open a PR via GitHub CLI.
  • Use cases include streamlining daily development, submitting work on multiple features, and ensuring standardized PRs.

Quick Start

Run pr-create to automatically turn your current changes into a pull request.

Frequently Asked Questions about pr-create

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

FAQPage Schema
How do I create a pull request from local commits automatically?

To create a pull request automatically, this skill assesses your repository state, commits local changes with conventional messages, pushes to a topic branch, and opens the PR via GitHub CLI.

Do I need Git and GitHub CLI installed to automate my PR workflow?

Yes, Git and GitHub CLI (gh) are required dependencies to automate your PR workflow, as the skill relies on them to detect branches, push changes, and open pull requests on your behalf.

Can I automatically create a topic branch from uncommitted changes before submitting a PR?

Yes, you can automatically create a topic branch from uncommitted changes; the skill detects your current branch status and creates a topic branch if needed before committing and opening the PR.

What is the best way to ensure consistent PR messaging across multiple feature branches?

The best way to ensure consistent PR messaging is to use an automated PR workflow that applies conventional commit messages and structured submission rules across all your feature branches.

How does automated base branch selection work when opening a GitHub pull request?

Automated base branch selection works by assessing your repository state, remote branches, and current log to determine the correct base branch automatically, or it prompts you for a preference before creating the PR.

Why does my automated pull request workflow fail on uncommitted local changes?

Your automated pull request workflow might fail if Git or GitHub CLI is missing, or if the skill cannot resolve the repository state to determine the correct base branch and topic branch for submission.