Verified:GitHub

pr-name

Generates correctly formatted pull request titles using package names and commit messages.

Updated May 15, 2026

Search Tags:#pull request #github #monorepo #package.json #commit message #naming convention

One-click install

npx skills add https://github.com/danielbere1973/promoar --skill pr-name-danielbere1973

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: pr-name
Source: https://github.com/danielbere1973/promoar/tree/main/.agents/skills/pr-name
Command: npx skills add https://github.com/danielbere1973/promoar --skill pr-name-danielbere1973

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Inconsistent pull request titles make changelogs hard to read and release tracking difficult, especially in monorepos where changes span multiple packages. ## Core Features & Use Cases - Standardized PR Titles: Enforces the format `[package-name]: [commit-message]` for every pull request. - Package Detection: Reads the package name from package.json and selects the most relevant package when multiple are affected. - Docs-Only Handling: Applies a simpler `Docs:` prefix format for documentation-only changes. - Use Case: When opening a PR that adds a heart shape to the shapes package, the title becomes `@remotion/shapes: Add heart shape` automatically. ## Quick Start Ask the assistant to name your pull request for the current changes and it will produce a correctly formatted title.

Frequently Asked Questions about pr-name

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

FAQPage Schema

How do I format a pull request title in a monorepo?▼

Use the format package-name followed by a colon and the commit message, such as @remotion/shapes: Add heart shape. The package name comes from the package.json of the affected package.

What PR title should I use when multiple packages are changed?▼

Pick the single package you consider most relevant to the change and use its name from package.json in the title. Do not list multiple package names in one title.

How do I name a pull request that only changes documentation?▼

Documentation-only pull requests skip the package name entirely and use the Docs prefix, for example Docs: Add page about heart shape.

Where does the package name in a PR title come from?▼

The package name is read directly from the name field in the package.json file of the affected package, ensuring the title matches the published package identifier.