create-pr

Push a feature branch and create a pull request with auto-generated title and body.

Updated Jan 15, 2026
One-click install
npx skills add https://github.com/nicolas-codemate/claudeCodeConfig --skill create-pr-nicolas-codemate
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-pr
Source: https://github.com/nicolas-codemate/claudeCodeConfig/tree/main/skills/create-pr
Command: npx skills add https://github.com/nicolas-codemate/claudeCodeConfig --skill create-pr-nicolas-codemate

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill streamlines the finalization of ticket-based work by pushing the feature branch and creating a properly targeted pull request, reducing manual steps and human error.

Core Features & Use Cases

  • Push to remote with upstream tracking for a deterministic workflow.
  • Detect target branch from multiple sources (explicit args, status files, ticket metadata, branch naming conventions, and config).
  • Create PR with auto-generated title and body, including draft mode support and idempotent checks.
  • Resolve common errors with guidance and safe fallback behavior.

Quick Start

Push the current feature branch and create a pull request to the detected target branch.

Frequently Asked Questions about create-pr

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

FAQPage Schema
How do I automatically push a feature branch and create a pull request?

You can automate pull request creation by pushing the feature branch with upstream tracking and generating a PR with an auto-generated title and body to the detected target branch.

How does target branch detection work when creating a pull request?

Target branch detection for pull request creation resolves from explicit arguments, status files, ticket metadata, branch naming conventions, config defaults, and Git defaults.

Can I create draft pull requests automatically with branch push automation?

Yes, pull request creation supports draft mode alongside automatic title and body generation, with idempotent checks to prevent duplicate PRs.

What is the best way to integrate YouTrack ticket metadata into GitHub pull request creation?

You can use ticket metadata from YouTrack integration to detect the target branch and auto-generate the pull request title and body for GitHub.

Why does my automated pull request creation fail when the target branch is ambiguous?

Pull request creation fails when the target branch cannot be resolved from explicit arguments, status files, ticket metadata, branch patterns, or config defaults, triggering robust error handling with guidance.