create-pr

Create feature branches, rebase onto main, and open GitHub PRs with labels.

1|Updated Feb 5, 2026

Search Tags:#git #workflow #github #rebase #branch #pull-request #conventional-commits

Ready to run

npx skills add https://github.com/jandragsbaek/codex-template --skill create-pr-jandragsbaek

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: create-pr
Source: https://github.com/jandragsbaek/codex-template/tree/main/.codex/skills/create-pr
Command: npx skills add https://github.com/jandragsbaek/codex-template --skill create-pr-jandragsbaek

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create a fresh feature branch from main, rebase on latest main, and open a GitHub PR with a solid summary and testing notes. Use when asked to “start a branch,” “rebase from main,” “open a PR,” or “get a PR going.”

Core Features & Use Cases

Branch creation from origin/main: Create a new feature branch from origin/main using a descriptive, conventional name.
Rebase onto origin/main: Rebase an existing branch onto origin/main to ensure up-to-date changes.
PR creation with labels and notes: Open a PR on GitHub with required labels and a detailed description including testing notes.
Branch naming and messaging: Infer a sensible branch name from scope and change type; maintains consistency with project conventions.

Quick Start

Use the create-pr skill to create a new feature branch from main, rebase onto latest main, and open a PR with a clear summary and testing notes.

Frequently Asked Questions about create-pr

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

FAQPage Schema

How do I open a GitHub pull request with a descriptive summary and testing notes?▼

To open a GitHub pull request with a descriptive summary, you can automate the process by creating a fresh feature branch from main, rebasing onto the latest main, and using the GitHub CLI to apply required PR labels and document testing notes.

What is the best way to create a feature branch from main and rebase onto the latest origin/main?▼

The best way to create a feature branch from main and rebase onto the latest origin/main is to use an automated workflow that infers a conventional branch name, ensures your changes are up-to-date, and prepares a clean PR foundation.

Can I enforce conventional commits and branch naming conventions when starting a PR?▼

Yes, you can enforce conventional commits and branch naming conventions by using a workflow that infers a sensible branch name from the scope and change type, maintaining consistency with your project's specific naming conventions.

Do I need the GitHub CLI to open a PR with required labels automatically?▼

Yes, you need the GitHub CLI to open a PR with required labels automatically, as the workflow relies on git and GitHub CLI commands to perform actions, enforce naming conventions, and apply labels.

Why should I rebase from main before opening a pull request?▼

You should rebase from main before opening a pull request to ensure your feature branch contains the most up-to-date changes from origin/main, preventing merge conflicts and maintaining a clean, linear project history.

Does this PR workflow handle applying required PR labels automatically?▼

Yes, this PR workflow handles applying required PR labels automatically by enforcing naming conventions and using GitHub CLI commands to perform actions, ensuring your pull request meets project requirements before submission.