skills.rest
hugotown
hugotownCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

pr-name

Generates pull request titles using package name and commit message conventions.

Updated Oct 16, 2025
Search Tags:#git#code review#pull request#monorepo#package.json#naming convention#pr title
One-click install
npx skills add https://github.com/hugotown/dotfiles --skill pr-name-hugotown
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pr-name
Source: https://github.com/hugotown/dotfiles/tree/main/agents/skills/pr-name
Command: npx skills add https://github.com/hugotown/dotfiles --skill pr-name-hugotown

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Inconsistent pull request titles make changelogs, release notes, and code history hard to scan. This Skill enforces a single, predictable PR title format so every contribution follows the same naming convention. ## Core Features & Use Cases - Standardized PR Titles: Formats titles as [package-name]: [commit-message], for example @remotion/shapes: Add heart shape. - Package Detection: Reads the package name from package.json and picks the most relevant package when multiple are affected. - Docs-Only Handling: Applies a simpler Docs: ... prefix when the change only touches documentation. - Use Case: You modified a component in a monorepo package and need a compliant PR title; the Skill inspects package.json and produces @myorg/ui: Fix button alignment. ## Quick Start Ask the assistant to name your pull request for the current changes and it will produce a title following the package-name convention.

Frequently Asked Questions about pr-name

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

FAQPage Schema
How do I write a pull request title for a monorepo change?▼

Use the format package-name followed by the commit message, such as @remotion/shapes: Add heart shape. Take the package name from package.json of the affected package, choosing the most relevant one if several packages changed.

What PR title format should I use for documentation-only changes?▼

Documentation-only changes skip the package prefix entirely. Use the format Docs: followed by a short summary, for example Docs: Add page about heart shape.

How is the package name determined when multiple packages are affected?▼

The package name is read from package.json of each affected package. When a change spans multiple packages, select the single package considered most relevant to the change and use its name in the title.

Can this PR naming convention be used outside the Remotion project?▼

Yes, the convention is generic: any repository with a package.json can adopt the package-name plus commit-message format. It works for both scoped npm packages and unscoped package names.

Related Skills

Explore More Software Engineering Skills→
inayayousfiinayayousfi
1

commit

Drafts and confirms Git commit messages before committing staged changes.

Community
Intermediate
liatrio-labsliatrio-labs
2

create-pull-request

Generate pull request titles and descriptions from git branch changes.

Official
Advanced
EtroxTaranEtroxTaran

pr-create

Create standardized GitHub pull requests with conventional commit titles and markdown descriptions.

Community
Intermediate
serejarisserejaris
215

git-workflow-manager

Enforce conventional commits, semantic versioning, and changelog updates for git releases.

Community
Basic