create-pull-request

Create GitHub pull requests with conventional titles and template-filled bodies.

Updated Jan 1, 2026
One-click install
npx skills add https://github.com/imvanzen/strava-kudosik --skill create-pull-request-imvanzen
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-pull-request
Source: https://github.com/imvanzen/strava-kudosik/tree/main/.cursor/skills/create-pull-request
Command: npx skills add https://github.com/imvanzen/strava-kudosik --skill create-pull-request-imvanzen

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the creation of GitHub pull requests by composing conventional titles, populating PR bodies from templates, and applying labels and assignees based on contextual information. It streamlines collaboration by turning a local branch into a ready-to-review PR without manual steps.

Core Features & Use Cases

  • Automated PR creation with conventional titles derived from contextual tokens like ticket numbers and scope.
  • Template-filled PR bodies using a GitHub MCP server to ensure consistent PR messaging.
  • Automatic labeling and assignees based on branch context and user inputs.
  • Use Case: You have a feature branch ready and want to open a PR for review with proper metadata.

Quick Start

Create a pull request for the current branch using the MCP server, extracting a ticket number and short description from your context to populate the title and body.

Frequently Asked Questions about create-pull-request

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

FAQPage Schema
How do I automate GitHub pull request creation from a local branch?

You can automate pull request creation by using an MCP server to extract contextual tokens like ticket numbers and scope, compose a conventional title, and call the GitHub API to open the PR automatically.

Can I automatically fill a PR template when opening a pull request?

Yes, the Skill reads an available PR template via a GitHub MCP server and populates the PR body automatically, ensuring consistent pull request messaging without manual formatting steps.

How do I add automatic labels and assignees when creating a pull request?

Automatic labels and assignees are applied based on branch context and user inputs during the pull request creation process, streamlining collaboration by assigning metadata dynamically.

What is a conventional title for a pull request and how is it generated?

A conventional title is generated by extracting commit types, ticket numbers, and scope from your context, then structuring these tokens into a standardized PR title format automatically.

Does pull request automation work without a pre-existing PR template?

Yes, the automation works by reading a PR template if one is available to populate the body, but it can still construct a conventional title and apply labels without an existing template.

What's the best way to declare a feature branch ready for code review?

The best way is to automate the process: extract context from the local branch, generate a conventional title, populate a template, and submit the PR for review with proper metadata attached.