skills.rest
JeremyKuhne
JeremyKuhneCOMMUNITY
Explore all skills by this author →
GitHub

create-pr

Create pull requests from feature branches to target main branches.

9|1|Updated Jun 6, 2025
Search Tags:#automation#git#github#pr#code-review#branch-management#pull-request
One-click install
npx skills add https://github.com/JeremyKuhne/touki --skill create-pr-jeremykuhne
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: create-pr
Source: https://github.com/JeremyKuhne/touki/tree/main/.agents/skills/create-pr
Command: npx skills add https://github.com/JeremyKuhne/touki --skill create-pr-jeremykuhne

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinating pull requests across feature branches can be error-prone and time-consuming. This skill standardizes how changes are prepared, reviewed, and merged by guiding users to create PRs that target the appropriate remote and avoid risky operations on main.

Core Features & Use Cases

  • Create PRs from a feature branch to a designated target (main) branch, with safeguards to keep main protected.
  • Ensure changes are on non-main branches and commits are ready for review, aligning with typical code-review workflows.
  • Supports both upstream and origin remotes, resolving the correct PR target based on repository configuration, and automating the review process for teams collaborating across forks.
  • Use case: a developer finishes a feature on a feature branch and submits a PR for teammate review before merging into main.

Quick Start

Create a feature branch, commit changes, and use this skill to open a PR targeting main on the appropriate remote.

Frequently Asked Questions about create-pr

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

FAQPage Schema
How do I automate pull request creation from a feature branch to main?▼

Automate pull request creation by using a skill that standardizes PR generation from feature branches to main, enforcing safe workflows and preventing risky operations like force pushes to protected branches.

How do I create a pull request across forks with different remotes?▼

Creating a pull request across forks is supported by resolving the correct PR target based on repository configuration, coordinating with both upstream and origin remotes to route the review appropriately.

Can I prevent force pushes to main when automating GitHub PR workflows?▼

Preventing force pushes to main is a core safeguard of this PR workflow automation, ensuring commits are gated and protected branches remain safe during collaborative code review.

Does this PR automation tool work with upstream and origin remotes?▼

This PR automation works with both upstream and origin remotes, resolving the correct target for pull requests based on your repository configuration across collaborative software projects.

What is the best way to ensure feature branch commits are ready for code review?▼

The best way to ensure commits are ready for code review is to standardize PR creation on non-main branches, aligning with typical workflows that gate commits and verify branch hygiene before merging.

Related Skills

Explore More Software Engineering Skills→
mhawthornemhawthorne
11

gza-code-review-interactive

Review committed changes on a feature branch against main.

Community
Advanced
Soul-Brews-StudioSoul-Brews-Studio
116

merged

Switch to main, pull latest changes, and delete merged branches.

Official
Basic
KanakMalpaniKanakMalpani

springboot-verification

Run build, static analysis, tests, security scans, and diff review for Spring Boot projects.

Community
Advanced
shawn-sandyshawn-sandy
2

pr-agent

Create GitHub pull requests from the current branch using the GitHub CLI.

Community
Intermediate