pr

Commit pending changes, push the branch, and create a GitHub pull request.

2|Updated Jan 22, 2026
One-click install
npx skills add https://github.com/abnegate/claudes --skill pr-abnegate
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr
Source: https://github.com/abnegate/claudes/tree/main/skills/pr
Command: npx skills add https://github.com/abnegate/claudes --skill pr-abnegate

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill reduces the friction of opening pull requests by automatically committing pending work, synchronizing with the remote branch, and generating a thorough PR description you can ship with confidence.

Core Features & Use Cases

  • Logical commit grouping: Delegates to skills:commit-all to turn uncommitted changes into sensible conventional-commit style commits before creating the PR.
  • Rich PR context generation: Pulls git status, commit history, diff stats, and remote sync information, then produces a concise summary, categorized change list, and an actionable test plan.
  • Automated PR creation: Pushes the current branch and uses GitHub CLI to open the pull request with a comprehensive body and a conventional title fallback.
  • Use case: When you finish a feature or bugfix across multiple files, run this Skill to produce a PR that reviewers can understand quickly and that includes a realistic test/checklist based on the changes.

Quick Start

Ask your AI to run the pr skill to commit your pending changes, push the branch, and open a GitHub pull request with an appropriate title and detailed description.

Frequently Asked Questions about pr

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

FAQPage Schema
How do I automate GitHub pull request creation from multiple local commits?

To automate GitHub pull request creation, you can commit pending changes, push the current branch, and generate a conventional commit-style title with a grouped changes section and test plan using local git history.

What is the best way to write a detailed PR description from a git diff?

The best way to write a detailed PR description from a git diff is to collect git status, commit history, and diff stats to generate a concise summary, categorized change list, and an actionable test plan for reviewers.

How do I generate a conventional commit-style PR title automatically?

Generating a conventional commit-style PR title automatically happens when no argument is provided, leveraging local git history and diffs to create an appropriate fallback title for the pull request.

Can I group uncommitted changes into logical commits before opening a pull request?

Yes, you can group uncommitted changes into logical commits before opening a pull request by delegating to commit automation that turns pending work into sensible conventional-commit style commits.

Does GitHub CLI work with automated release workflows for code collaboration?

Yes, GitHub CLI integrates with automated release workflows by running gh pr create to open a pull request with a comprehensive body after pushing the current branch and assembling local git history.

When do I need to include an actionable test plan in my pull request body?

You need to include an actionable test plan in your pull request body when finishing a feature, bugfix, or refactor across multiple files, ensuring reviewers understand the changes and verification steps.