create-pr

Create GitHub pull requests with titles formatted for check-pr-title validation.

Updated Aug 23, 2026

Search Tags:#automation #github #code-review #pull-request #conventional-commits #title-formatting

Ready to run

npx skills add https://github.com/alishangtian/proteus-ai --skill create-pr-alishangtian

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: create-pr
Source: https://github.com/alishangtian/proteus-ai/tree/main/proteus/docker/volumes/agent/skills/create-pr
Command: npx skills add https://github.com/alishangtian/proteus-ai --skill create-pr-alishangtian

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Creates GitHub PRs with properly formatted titles that pass the check-pr-title CI validation. Use when creating PRs, submitting changes for review, or when the user says /pr or asks to create a pull request.

Core Features & Use Cases

Formatting: Ensures PR titles follow the type(scope): summary convention.
Validation: Checks conformance with check-pr-title requirements.
Automation: Integrates with tools to draft and open PRs from chat/CLI.

Quick Start

Tell Proteus the PR type, scope (optional), and a short summary to generate a compliant title and open the PR.

Frequently Asked Questions about create-pr

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

FAQPage Schema

How do I create a GitHub pull request with a title that passes check-pr-title validation?▼

To create a GitHub pull request that passes check-pr-title validation, format the title using the type(scope): summary convention to ensure conformance with CI requirements before opening the PR.

What is the conventional commits format required for GitHub PR titles?▼

The conventional commits format for PR titles requires specifying a type, an optional scope, and a required summary, structured as type(scope): summary to pass automated CI validation.

How do I automate GitHub PR creation from the command line or chat?▼

Automate GitHub PR creation by providing the PR type, optional scope, and short summary, which triggers deterministic logic to construct a compliant title and open the pull request automatically.

Does this PR formatting approach work for fixes, tests, and documentation changes?▼

Yes, this PR formatting approach works for features, fixes, tests, and documentation changes, applying optional scope and required summary rules based on the specific PR type.

Why does my GitHub PR title fail CI validation despite having a clear description?▼

Your GitHub PR title fails CI validation because it lacks the required conventional commits structure, which mandates a specific type, optional scope, and summary format to pass check-pr-title.

What is the best way to format a pull request title for automated code review checks?▼

The best way to format a pull request title for automated code review checks is to use a deterministic workflow that validates and constructs the title from type, scope, and summary components.