pull-request

Draft an intent-focused GitHub pull request from the current git branch against main.

8|1|Updated Mar 1, 2026
One-click install
npx skills add https://github.com/JoeCP17/LLM-Dot-files --skill pull-request-joecp17
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pull-request
Source: https://github.com/JoeCP17/LLM-Dot-files/tree/main/codex/skills/pull-request
Command: npx skills add https://github.com/JoeCP17/LLM-Dot-files --skill pull-request-joecp17

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Creates clear, intent-focused GitHub pull requests from the current branch so reviewers understand why the change exists, while preventing common mistakes like dirty working trees or duplicate PRs.

Core Features & Use Cases

  • Drafts a PR title in the required format and writes a sectioned PR body with English ## headings and concise bullets.
  • Enforces guardrails such as branch-name prefixes (feature/bugfix/refactor), clean working tree, existing origin remote, successful fetch to main, and no existing open PR for the branch.
  • Pushes to origin when upstream is missing or when needed, then creates the PR against main using GitHub CLI (gh).
  • Use Case: When a Korean collaboration context exists, it keeps PR body language aligned with repository norms while using terse, review-friendly Korean bullet content for Korean lines.

Quick Start

Use the pull-request skill to review your current git branch, draft the PR title and sectioned body, ask you to confirm, then push (if needed) and open a GitHub PR against main.

Frequently Asked Questions about pull-request

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

FAQPage Schema
How do I create a GitHub pull request from a local git branch using the command line?

You can create a GitHub pull request by running the gh CLI against your current local branch. The skill drafts an intent-focused PR title and sectioned body from the diff vs origin/main, asks for confirmation, then pushes and opens the PR.

What's the best way to automate writing clear PR descriptions for code review?

Automating clear PR descriptions is done by generating a sectioned PR body with concise bullets from the branch diff. This ensures reviewers understand the intent behind feature, bugfix, or refactor changes without manual formatting effort.

Do I need the GitHub CLI installed to open a pull request from my local repository?

Yes, an authenticated GitHub CLI (gh) is required to create the pull request end-to-end. The skill relies on gh to push to the origin remote and open the PR against the main branch after you confirm the draft.

Can I create a pull request if my git working tree has uncommitted changes?

No, creating a pull request requires a clean working tree. The skill enforces guardrails that block PR creation if uncommitted changes exist, ensuring only reviewed and committed code is pushed and submitted.

Does this pull request workflow support branches without the feature, bugfix, or refactor prefix?

No, branch prefix validation restricts PR creation to feature/, bugfix/, and refactor/ branches. This naming convention ensures the generated PR title and body align with the specific intent of the code changes being submitted.

Why does my pull request creation fail when an open PR already exists for my branch?

Pull request creation fails because duplicate PR detection is a mandatory guardrail. The skill checks for existing open PRs on your branch before drafting, preventing redundant review threads and keeping collaboration focused on a single request.