gh:pr

Automates GitHub pull request creation with issue linking and duplicate prevention.

2|Updated Jan 30, 2026
One-click install
npx skills add https://github.com/amdmax/claude_marketplace --skill gh-pr-amdmax
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gh:pr
Source: https://github.com/amdmax/claude_marketplace/tree/main/skills/gh%3Apr
Command: npx skills add https://github.com/amdmax/claude_marketplace --skill gh-pr-amdmax

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 they are properly linked to issues, include relevant commit history, and prevent duplicates.

Core Features & Use Cases

  • Automated Commit: Commits uncommitted changes before creating a PR.
  • Issue Linking: Automatically links PRs to active GitHub issues or creates new ones.
  • Duplicate Prevention: Checks for and prevents the creation of duplicate PRs.
  • Use Case: After finishing a feature, run /pr to automatically commit your work, create a PR linked to the relevant story, and get a confirmation message with the PR URL.

Quick Start

Run the /pr command to create a pull request for your current changes.

Frequently Asked Questions about gh:pr

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

FAQPage Schema
How do I automate GitHub pull request creation from uncommitted changes?

Automating GitHub pull request creation requires committing uncommitted local changes first. This Skill handles that automatically, linking the new PR to active GitHub issues and streamlining your development workflow.

How do I link a pull request to an active GitHub issue automatically?

To link a pull request to an active GitHub issue automatically, this Skill integrates issue tracking with commit history. It matches your current work to relevant stories and includes the issue links in the PR.

How can I check for and prevent duplicate pull requests in my workflow?

Preventing duplicate pull requests is handled by checking existing PRs against your current changes before creation. This duplicate prevention mechanism ensures you do not open redundant requests for the same work.

What is the best way to integrate commit history into a new pull request?

The best way to integrate commit history into a new pull request is using an automated workflow tool. This Skill compiles relevant commits, links active issues, and generates the PR with full context.

Does this automated pull request workflow require any external dependencies?

This automated pull request workflow operates without external dependencies. It functions independently using internal scripts and references to manage commits, link issues, and create GitHub PRs.