create-pr

Create pull requests with templates and branch naming conventions.

11|Updated Jan 25, 2026
One-click install
npx skills add https://github.com/BangDori/prowl --skill create-pr-bangdori
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-pr
Source: https://github.com/BangDori/prowl/tree/main/.agents/skills/create-pr
Command: npx skills add https://github.com/BangDori/prowl --skill create-pr-bangdori

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill streamlines the process of creating Pull Requests by ensuring adherence to project conventions and templates, reducing manual effort and potential errors.

Core Features & Use Cases

  • Automated PR Creation: Generates Pull Requests based on predefined templates and branch naming conventions.
  • Changeset Management: Integrates with changesets for versioning and release notes, with logic to determine necessity.
  • Convention Enforcement: Validates branch naming and PR title formats.
  • Use Case: After completing a new feature, use this Skill to automatically push your branch, create a PR with the correct template, and ensure all necessary checks are in place.

Quick Start

Use the create-pr skill to generate 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 automate pull request creation with branch naming conventions in GitHub?

Automating pull request creation validates branch names like feat/ or fix/ and uses gh pr create with GITHUB_TOKEN to generate PRs against the develop branch automatically.

Can I enforce PR title formats and target branches when creating a GitHub pull request?

PR title formats and target branches are enforced during PR creation by validating branch naming conventions and automatically targeting the develop branch using the gh pr create command.

How do changesets integrate with pull request generation for versioning?

Changesets integrate with pull request generation by evaluating branch types and determining versioning necessity, automatically generating changeset files to track release notes alongside the PR creation process.

What is the best way to ensure a new feature branch follows project templates before pushing?

Ensuring a feature branch follows templates requires validating the branch name against project conventions like enhance/ or refactor/, then automatically applying predefined PR templates during the push and PR creation workflow.

Do I need a GITHUB_TOKEN to automate pull request creation with changesets?

A GITHUB_TOKEN is required to automate pull request creation, as the gh pr create command uses this token to authenticate and push branches while generating changesets for release notes.

What branch prefixes are supported when automating GitHub PR creation?

Supported branch prefixes include feat/, fix/, enhance/, refactor/, test/, and chore/, which are validated during automated PR creation to ensure compliance with project naming conventions.