ah-create-pr

Create or update GitHub pull requests from the current git branch.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/arinhubcom/arinhub-dev-skills --skill ah-create-pr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ah-create-pr
Source: https://github.com/arinhubcom/arinhub-dev-skills/tree/main/skills/ah-create-pr
Command: npx skills add https://github.com/arinhubcom/arinhub-dev-skills --skill ah-create-pr

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Creates and updates GitHub Pull Requests from the current branch, ensuring a consistent PR structure, including a generated summary, diff, and linked issues, while preventing duplicate PRs for the same branch.

Core Features & Use Cases

  • Automates PR creation and updates from the active branch, including generating a summary, diff, and linked issues.
  • Validates required input (base branch) and handles optional inputs like issue number and labels, ensuring proper PR metadata and formatting.
  • Integrates with GitHub CLI to create or edit PRs, and gracefully handles existing PRs targeting the same base or a different base.

Quick Start

Provide the base branch and optional issue number or labels, then run the skill to create or update the PR from your current branch.

Frequently Asked Questions about ah-create-pr

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

FAQPage Schema
How do I automatically create a GitHub pull request from my current branch?

To automatically create a GitHub pull request, you must provide the target base branch, while issue numbers and labels are optional. The tool computes the diff against the base and uses the GitHub CLI to publish a structured PR with linked issues.

How do I update an existing pull request if one is already open for my branch?

To update an existing pull request, the tool detects an open PR for the same branch and uses the GitHub CLI to edit it. It gracefully handles PRs targeting the same base or a different base branch to prevent duplicates.

What happens if I don't specify a base branch when automating PR creation?

Automating PR creation requires a base branch as a mandatory input. Without specifying the base branch, the process enforces validation and stops to ensure proper PR metadata and structural formatting before proceeding.

Does this PR automation tool work with the GitHub CLI?

Yes, the PR automation tool integrates directly with the GitHub CLI, specifically using the gh pr create and gh pr edit commands to publish and update pull requests from the current git branch.

Can I attach issue numbers and labels when generating a pull request from a branch?

Yes, you can attach issue numbers and labels when generating a pull request. These are handled as optional inputs that ensure proper PR metadata, formatting, and issue linking within the automated workflow.

How does automating pull requests handle diffs against the base branch?

Automating pull requests computes the code diff against the specified base branch to generate a well-structured PR summary. This ensures the published pull request accurately reflects branch changes and linked issues.