skills.rest
junkisai
junkisaiCOMMUNITY
Explore all skills by this author →
GitHub

pr

Create a branch from current changes, commit, push, and open a GitHub PR.

1|Updated Oct 21, 2023
Search Tags:#automation#git#workflow#branch#pull-request#main-branch
One-click install
npx skills add https://github.com/junkisai/web-app-template --skill pr-junkisai
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pr
Source: https://github.com/junkisai/web-app-template/tree/main/.agents/skills/pr
Command: npx skills add https://github.com/junkisai/web-app-template --skill pr-junkisai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The skill automates turning current changes on the main branch into a new feature branch, commits them, and opens a GitHub Pull Request, enforcing main-only execution.

Core Features & Use Cases

  • Create a new branch from the current changes built from your working tree
  • Commit changes, push to the new branch, and open a PR with a standard template
  • Use Case: When you want to convert your current changes into a review-ready PR without manual multi-step steps.

Quick Start

Create a new branch from your current changes, commit, push, and open a PR.

Frequently Asked Questions about pr

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

FAQPage Schema
How do I automatically create a new branch and open a GitHub pull request from my current changes?▼

You can automate creating a pull request by using a workflow that reads working tree diffs, generates a short kebab-case branch, commits the changes, pushes them, and opens a PR with a standard template.

How can I convert my current working tree changes into a review-ready GitHub PR without manual steps?▼

To convert working tree changes into a review-ready PR automatically, a workflow checks the main branch, isolates your changes onto a new branch, commits, pushes, and opens a PR using a standard template.

Does the automated pull request workflow require changes to be made directly on the main branch?▼

Yes, this automated PR workflow applies to main-repo workflows and enforces main-only execution, ensuring your local changes are isolated onto a new feature branch before being pushed and submitted for review.

How does the branch naming work when automating a pull request from uncommitted changes?▼

Branch naming is handled automatically by reading the current diffs from your working tree and generating a short kebab-case branch name to isolate the committed changes before opening the pull request.

What is the best way to enforce a standard template when opening a GitHub pull request automatically?▼

The best way to enforce a standard PR template automatically is to use a workflow that commits current changes to a new branch, pushes, and generates the pull request with a predefined standard template.

Can I use this automation if my current changes are already committed to a feature branch instead of the main branch?▼

No, this automation enforces main-only execution and is designed specifically for main-repo workflows where uncommitted changes on the main branch need to be isolated onto a new branch before opening a PR.

Related Skills

Explore More Software Engineering Skills→
ahandselahandsel
1

git-pull-main

Synchronizes local Git feature branches with the remote main branch.

Community
Intermediate
JacobPEvansJacobPEvans
3

rebase-pr

Rebase pull requests onto main with signed commits and GitHub API checks.

Community
Advanced
cbleckercblecker
5

creating-pull-request

Automate GitHub pull request creation with branch pushing and PR metadata.

Community
Basic
brandonalfredbrandonalfred
2

draft-pr

Create and push draft pull requests from GitHub feature branches.

Community
Intermediate