pr

Generate a complete pull request from a GitHub issue.

7|3|Updated Jul 31, 2025
One-click install
npx skills add https://github.com/seabbs/claude-code-config --skill pr-seabbs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr
Source: https://github.com/seabbs/claude-code-config/tree/main/skills/pr
Command: npx skills add https://github.com/seabbs/claude-code-config --skill pr-seabbs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the creation of a complete pull request from a GitHub issue, including issue analysis, implementation scaffolding, QA steps, and PR creation, reducing manual coordination and cycle time.

Core Features & Use Cases

  • Issue analysis and scoping based on the referenced GitHub issue.
  • Automated implementation planning, including branch naming and worktree guidance.
  • End-to-end QA, linting, and validation before PR submission.
  • Auto-generates a well-structured PR with summary, changes, and testing notes.

Quick Start

Provide an issue number to generate a complete PR for that issue.

Frequently Asked Questions about pr

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

FAQPage Schema
How do I automate pull request creation from a GitHub issue?

To automate pull request creation from a GitHub issue, provide the issue number to generate a complete PR. This includes issue analysis, implementation scaffolding, QA validation, and structured PR submission with summaries and testing notes.

Does this automated PR workflow handle branch naming and worktree setup?

Yes, the automated PR workflow handles branch naming and worktree setup. It applies structured branch naming conventions and provides worktree guidance during the implementation planning phase before code changes begin.

Can I use this to generate code for small bugs and feature improvements?

Yes, you can use this to generate code for small bugs and feature improvements. The workflow assesses issue complexity and handles GitHub issues ranging from minor bug fixes to clear feature improvements with proper issue references.

How does automated pull request generation handle QA and linting?

Automated pull request generation handles QA and linting by running end-to-end validation before submission. The workflow performs final verification, linting, and QA steps to ensure the implementation meets project standards before creating the PR.

What is the best way to turn GitHub issues into ready-to-merge pull requests?

The best way to turn GitHub issues into ready-to-merge pull requests is to automate issue analysis, implementation, and QA into a single workflow. This approach generates a structured PR with a summary, changes, and testing notes from a given issue number.

What types of GitHub issues are not suitable for automated PR generation?

GitHub issues lacking clear references or well-defined scope are not suitable for automated PR generation. The workflow requires a clear issue description to properly analyze complexity, scaffold the implementation, and generate a structured pull request.