open-pull-request

Create draft pull requests with conventional branch names and commit titles.

3|Updated Mar 20, 2026
One-click install
npx skills add https://github.com/alkofu/ai-tpk --skill open-pull-request-alkofu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: open-pull-request
Source: https://github.com/alkofu/ai-tpk/tree/main/claude/skills/open-pull-request
Command: npx skills add https://github.com/alkofu/ai-tpk --skill open-pull-request-alkofu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill ensures PRs follow a consistent workflow by enforcing conventional branch names and conventional-commit PR titles across repositories.

Core Features & Use Cases

  • Enforces conventional branch naming (<type>/<description>) and conventional commit titles for PR creation.
  • Automates draft PR creation, assignment to the user, and guides the PR workflow from branch to merge.
  • Use case: when collaborating on a feature branch, automatically generate a properly formatted PR with required conventions.

Quick Start

Draft a pull request using a conventional branch name and a conventional commit title, create it as a draft, and assign it to the current user.

Frequently Asked Questions about open-pull-request

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

FAQPage Schema
How do I automate draft PR creation with conventional commit titles?

Automating draft PR creation requires enforcing conventional commit titles and branch names. This skill validates your branch naming format, formats commit messages, pushes changes, and opens a draft PR assigned to you.

Does this PR workflow automation work with both GitHub and GitLab?

Yes, this PR workflow automation works with GitHub and GitLab. It applies conventional branch naming and commit title validation across platforms, supporting commands like gh pr create and glab mr create for automated drafting.

How do I enforce conventional branch naming before opening a pull request?

To enforce conventional branch naming before opening a pull request, the skill inspects your repository state and validates the <type>/<description> branch format. It performs pre-push validation to ensure compliance before drafting.

What is the best way to standardize pull request conventions across repositories?

The best way to standardize pull request conventions is to automate the end-to-end workflow. This skill enforces conventional commit titles and branch naming, handling conflict resolution, automated assignment, and draft creation consistently.

Can I handle merge conflicts automatically when creating a draft PR?

Yes, you can handle merge conflicts when creating a draft PR. The skill includes conflict handling steps within its automated workflow to guide resolution before pushing and opening the conventional draft pull request.