pr

Commit staged changes, push to remote, and create a GitHub pull request.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the process of sharing your code changes by automating the commit, push, and pull request creation workflow, saving you manual steps and ensuring consistency.

Core Features & Use Cases

  • Automated Git Workflow: Commits staged changes, pushes to the remote, and creates a GitHub pull request.
  • Context-Aware: Detects base branches, analyzes diffs for commit messages, and links to GitHub issues.
  • Use Case: After completing a new feature, you can simply say "pr" and the Skill will handle all the necessary Git commands and GitHub interactions to get your code reviewed.

Quick Start

Use the pr skill to commit, push, and create a pull request for your current changes.

Frequently Asked Questions about pr

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

FAQPage Schema
How do I automate a git commit, push, and pull request in one step?

You can automate a git commit, push, and pull request in one step by running a workflow that analyzes staged Git diffs, generates conventional commit messages, pushes to a remote repository, and creates a GitHub pull request automatically.

Can I automatically link related GitHub issues when creating a pull request?

Yes, you can automatically link related GitHub issues when creating a pull request. The automation analyzes your Git diffs to detect related issues and includes them in the generated PR titles and bodies.

Do I need the GitHub CLI installed to automate pull request creation?

Yes, you need the GitHub CLI (gh) installed and authenticated to automate pull request creation. The workflow relies on the gh command-line tool to interact with GitHub and create the pull request.

How does automated commit message generation work from git diffs?

Automated commit message generation works by analyzing your staged Git diffs to understand the code changes. It then uses this context to generate standardized conventional commit messages and corresponding PR titles and bodies.

What is the best way to create a GitHub pull request after staging changes?

The best way to create a GitHub pull request after staging changes is to use an automation tool that detects the base branch, commits the staged changes, pushes to the remote, and executes the PR creation via GitHub CLI.