skills.rest
Namacha411
Namacha411COMMUNITY
Explore all skills by this author →
Website𝕏@namacha_411GitHub

pr

Push the current branch to origin and create a GitHub pull request with gh pr create.

Updated May 11, 2022
Search Tags:#git#pull request#conventional commits#github#gh cli#git push
One-click install
npx skills add https://github.com/Namacha411/dotfiles --skill pr-namacha411
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pr
Source: https://github.com/Namacha411/dotfiles/tree/main/shared/claude/skills/pr
Command: npx skills add https://github.com/Namacha411/dotfiles --skill pr-namacha411

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you open a GitHub pull request quickly and consistently by guiding the steps from creating a commit to using the GitHub CLI to open the PR.

Core Features & Use Cases

  • Stages and commits changes via another skill: Uses the commit workflow to produce the right commit message format and confirmations before you move on.
  • Validates the current branch: Ensures you push the correct branch by checking what git branch --show-current reports.
  • Pushes and creates the PR via GitHub CLI: Pushes to origin and opens a PR with gh pr create using a descriptive title and summary.

Quick Start

Stage and commit your changes with the commit skill, then run this PR flow to push the current branch and open a GitHub pull request with a clear title and summary.

Frequently Asked Questions about pr

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

FAQPage Schema
How do I create a GitHub pull request from committed changes using gh cli?▼

You create a GitHub pull request by pushing the current branch to origin and invoking `gh pr create` with a meaningful title and body. This workflow applies to collaborative environments where code is reviewed via pull requests.

What's the best way to ensure I push the correct git branch before opening a pull request?▼

Verifying your git branch before opening a pull request involves checking the output of `git branch --show-current`. This ensures you push the correct branch to origin before invoking `gh pr create`.

Does this pull request workflow require conventional commits?▼

This pull request workflow applies to collaborative environments where commit history should follow a conventional format. It relies on a separate commit workflow to stage changes and produce the correct commit message format before pushing.

How do I push staged commits to GitHub and open a PR?▼

To push staged commits to GitHub, you first prepare and commit your staged changes using a commit workflow. Then you push the current branch to origin and use `gh pr create` to open a pull request with a descriptive title and summary.

Do I need to authenticate git push separately before using gh pr create?▼

Yes, the workflow requires authenticated git push to push the current branch to origin. You must ensure your git and GitHub CLI environment is properly authenticated before running the pull request creation flow.

Related Skills

Explore More Software Engineering Skills→
mhattingpetemhattingpete
657

git-pushing

Stage, commit, and push code changes with conventional commit messages.

Community
Basic
ybbms777ybbms777
1

resolve-pr-feedback

Process GitHub pull request review feedback end-to-end with gh and jq.

Community
Advanced
gelowzzzgelowzzz

ship-it

Push the current Git branch to GitHub and open a pull request with generated title and body.

Community
Intermediate
brandonalfredbrandonalfred
2

draft-pr

Create and push draft pull requests from GitHub feature branches.

Community
Intermediate