skills.rest
yairbederman
yairbedermanCOMMUNITY
Explore all skills by this author →
GitHub

create-pr

Generate GitHub PR titles in conventional-commit format.

Updated Dec 24, 2025
Search Tags:#git#pr#code-review#pull-request#conventional-commit#title-formatting
One-click install
npx skills add https://github.com/yairbederman/EngineeringAgency --skill create-pr-yairbederman
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: create-pr
Source: https://github.com/yairbederman/EngineeringAgency/tree/main/skills/create-pr
Command: npx skills add https://github.com/yairbederman/EngineeringAgency --skill create-pr-yairbederman

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

PR titles often fail to follow a consistent convention, making it harder to review changes and track changes across a codebase. This skill enforces a standard PR-title format to improve clarity and automation in code review workflows.

Core Features & Use Cases

  • Enforces conventional-commit style: Ensures PR titles follow the <type>(<scope>): <summary> pattern.
  • Scope guidance: Encourages meaningful scopes like API, core, editor, ui, or module areas to improve traceability.
  • Validation & Safety: Checks for required type and optional breaking-change suffix handling, and prevents trailing periods in the summary.

Quick Start

Invoke the PR creation flow to generate a conventional-commit style title for your changes.

Frequently Asked Questions about create-pr

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

FAQPage Schema
How do I generate conventional commit titles for GitHub pull requests?▼

You can generate conventional commit PR titles by enforcing the <type>(<scope>): <summary> pattern, which validates required fields and supports optional breaking change suffixes for consistent code review tracking.

What is the conventional commit format for pull request titles?▼

The conventional commit format for PR titles follows the <type>(<scope>): <summary> pattern, ensuring consistent naming across features, bug fixes, and improvements in frontend, backend, or tooling workflows.

How do I add a breaking change suffix to a PR title?▼

To add a breaking change suffix to a PR title, the generation flow validates the optional breaking change notation and ensures the summary does not end with a trailing period.

What scopes should I use for conventional commit PR titles?▼

Meaningful scopes for conventional commit PR titles include API, core, editor, ui, or specific module areas to improve traceability across the codebase during code review.

Does this PR title generator work for both frontend and backend code changes?▼

Yes, the PR title generator applies across features, bug fixes, and improvements in both frontend and backend workflows, as well as tooling changes, ensuring consistent GitHub PR naming.

How do I handle PR titles that do not require a changelog entry?▼

The PR title generation flow supports no-changelog handling, allowing you to format pull request titles for changes that do not require changelog tracking while maintaining the conventional commit structure.

Related Skills

Explore More Software Engineering Skills→
mgoodman60mgoodman60

commit

Generate descriptive Git commit messages from repository changes with conventional formatting.

Community
Basic
module-federationmodule-federation
2.6k

gh-pr-metadata

Normalize GitHub Pull Request titles to conventional commit format and rewrite bodies to match repository templates.

Official
Intermediate
vikisingh23vikisingh23
4

changelog

...

Community
Intermediate
co-labs-coco-labs-co
1

conventional-commits-release

Validate commit messages and PR titles with commitlint for automated semantic-release versioning.

Official
Intermediate