skills.rest
abretonc7s
abretonc7sCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

pr-title

Generate conventional pull request titles from branch names and change descriptions.

Updated Apr 10, 2026
Search Tags:#git#pull request#conventional commits#pr#title formatting
One-click install
npx skills add https://github.com/abretonc7s/metamask-skills --skill pr-title-abretonc7s
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pr-title
Source: https://github.com/abretonc7s/metamask-skills/tree/main/domains/pr-workflow/skills/pr-title
Command: npx skills add https://github.com/abretonc7s/metamask-skills --skill pr-title-abretonc7s

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Inconsistent and unclear pull request titles can hinder project tracking and collaboration, leading to confusion and reduced productivity.

Core Features & Use Cases

  • Consistent Formatting: Enforces conventional commit-style titles with scope and type indicators.
  • Quality Control: Guides developers to write clear, concise, and informative PR titles before submission.
  • Use Case: When preparing a pull request for a new feature in the wallet module, use this Skill to generate a compliant PR title like 'feat(wallet): add transaction history'.

Quick Start

Use the pr-title skill to create a proper PR title based on your current branch and changes.

Frequently Asked Questions about pr-title

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

FAQPage Schema
How do I format a pull request title using conventional commits?▼

Format a pull request title using conventional commits by applying type and scope indicators to your changes. This generates standardized titles like 'feat(wallet): add transaction history', ensuring clear project documentation and streamlined code review processes.

What is the conventional commit format for PR titles?▼

The conventional commit format for PR titles structures descriptions using specific type and scope indicators. This enforces consistent formatting across development teams, clarifying the nature of changes before code review and submission.

How do I generate a standardized PR title from a branch name?▼

Generate a standardized PR title from a branch name by analyzing the branch identifier alongside change descriptions. This requires access to current branch names and change details to accurately construct compliant conventional commit titles.

Why do my pull request titles fail conventional commit checks?▼

Pull request titles fail conventional commit checks when they lack proper type and scope indicators. Standardizing titles with the correct conventional format resolves these quality control issues, guiding developers to write clear and informative PR titles.

Can I enforce conventional commit PR titles for my team?▼

You can enforce conventional commit PR titles for your team by standardizing the creation process. This enforces consistent formatting with scope and type indicators, aiding project tracking and collaboration while reducing confusion across development teams.

Related Skills

Explore More Software Engineering Skills→
Women-Coding-CommunityWomen-Coding-Community
10

open-pr

Create GitHub pull requests with conventional commit titles and descriptions.

Official
Intermediate
TobiasGoetzTobiasGoetz

commit

Generate conventional commit messages and PR titles for Release Please.

Community
Intermediate
Cogni-DAOCogni-DAO

pull-request

Generate Conventional Commit PR titles and summaries for staging branch merges.

Official
Intermediate
PAIPaloozaPAIPalooza
2

git-workflow

Enforce strict Git commit and Pull Request standards without AI attribution.

Official
Intermediate