skills.rest
sam-evolv
sam-evolvCOMMUNITY
Explore all skills by this author →
GitHub

create-pr

Create GitHub pull requests with conventional titles via gh CLI.

Updated Oct 28, 2025
Search Tags:#automation#git#github#pr#pull-request#gh-cli#title-validation
One-click install
npx skills add https://github.com/sam-evolv/property-assistant --skill create-pr-sam-evolv
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: create-pr
Source: https://github.com/sam-evolv/property-assistant/tree/main/.skills/create-pr
Command: npx skills add https://github.com/sam-evolv/property-assistant --skill create-pr-sam-evolv

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates the creation of GitHub pull requests by generating properly formatted titles that pass the check-pr-title CI validation.

Core Features & Use Cases

  • Enforces conventional PR title format: type(scope): summary
  • Works across multiple repositories via gh CLI and git
  • Use Case: When submitting changes, this skill ensures PR titles are consistent and CI-ready.

Quick Start

Use the create-pr skill to open a PR with a properly formatted title for a new feature.

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 conventional commit title format?▼

To create a GitHub pull request with a conventional title format, you must structure the title as type(scope): summary. This ensures the PR title passes check-pr-title CI validation and maintains consistency across multiple repositories.

Why does my pull request fail check-pr-title CI validation?▼

Your pull request fails check-pr-title CI validation because the title does not match the required type(scope): summary pattern. Automating PR creation validates the type, scope, and summary against this convention before submission.

Can I use gh CLI to automate pull request title validation across multiple repositories?▼

Yes, you can use gh CLI to automate pull request title validation across multiple repositories. The CLI works with git workflows to enforce the conventional PR title format, ensuring titles are CI-ready before opening the request.

What is the correct format for a conventional PR title?▼

The correct format for a conventional PR title is type(scope): summary. This pattern separates the commit type, the scope of the change, and a brief summary, which check-pr-title validation requires to pass CI.

Does automating PR creation work with existing Git workflows?▼

Yes, automating PR creation works with existing Git workflows. It integrates directly with gh CLI and git to validate the title format and open the pull request without disrupting your current development process.

What are the limitations of enforcing PR title conventions?▼

The limitation of enforcing PR title conventions is that titles must strictly follow the type(scope): summary pattern. Any deviation from this format will cause the check-pr-title validation to fail, blocking the pull request.

Related Skills

Explore More Software Engineering Skills→
NVIDIANVIDIA
8.1k

review-github-pr

Summarize GitHub pull request diffs and identify key design decisions.

Official
Advanced
kk20300113-pngkk20300113-png

land-and-deploy

Merge pull requests and verify production health via canary checks.

Community
Advanced
alirezarezvanialirezarezvani
763

git-commit-helper

Generate conventional commit messages from staged git diff changes.

Community
Basic
brivarobrivaro

prowler-ci

Diagnoses and resolves GitHub Actions CI check and pull request gate failures.

Community
Intermediate