create-pr

Name: create-pr
Availability: InStock
Author: Prisma

Generate GitHub pull requests with conventional commit titles and narrative descriptions.

419|15|Updated Oct 31, 2025

Search Tags:#automation #git #code review #pull request #conventional commits #github

Ready to run

npx skills add https://github.com/prisma/prisma-next --skill create-pr-prisma

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the creation of GitHub Pull Requests, ensuring they adhere to conventional commit standards for titles and include a detailed, narrative description derived from your commit history.

Core Features & Use Cases

Automated PR Title Generation: Creates titles following the type(scope): description format.
Narrative PR Description: Compiles commit logs and diffs into a structured, human-readable description.
Linear Ticket Integration: Prompts for and incorporates Linear ticket information into the PR.
Use Case: After completing a set of features on a new branch, use this Skill to generate a well-formatted PR ready for review, complete with a clear title and a comprehensive description of the changes and their intent.

Quick Start

Use the create PR skill to prepare a pull request for the current 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 generate a GitHub pull request with conventional commits?▼

To generate a GitHub pull request with conventional commits, this Skill analyzes your commit history and code diffs to produce a PR title in the `type(scope): description` format and a structured narrative description.

What is the best way to create a structured PR description from commit history for code review?▼

The best way to create a structured PR description from commit history is to use an automation tool that compiles commit logs and diffs into a human-readable walkthrough of changes, facilitating clearer code review.

Can I integrate Linear ticket information into my GitHub PR title and description?▼

Yes, you can integrate Linear ticket information into your GitHub PR. The Skill prompts for Linear issue tracking details and incorporates that context directly into the generated pull request.

Does the generated pull request title follow the conventional commits format?▼

Yes, the generated pull request title strictly follows the conventional commits format, automatically structuring your PR title into the standard `type(scope): description` syntax based on the analyzed changes.

How do I prepare a pull request for review after completing features on a new branch?▼

To prepare a pull request for review after completing features on a new branch, run the automation to compile your commit logs and diffs into a well-formatted PR with a clear title and comprehensive description.

What context does the automated PR description include for code reviewers?▼

The automated PR description includes structured context for code reviewers, detailing commit types, scopes, and a comprehensive walkthrough of the code changes derived from your diff analysis.