Pr Name

If you work in a monorepo and are tired of inconsistent PR titles, this enforces a clean format: backtick-wrapped package name from package.json, followed by a colon and commit message, like `@remotion/shapes`: Add heart shape. It handles the common case where a PR touches multiple packages by having you pick the most relevant one, and includes a special Docs: prefix for documentation-only changes. Simple rule, but it keeps your PR history scannable when you've got dozens of packages flying around. Worth adding if your team keeps forgetting which package a change actually belongs to.

skills.sh installs: 1.1K
GitHub stars: 72.1K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add remotion-dev/remotion --skill pr-name --agent claude-code

Installs into .claude/skills of the current project.

Files

When given a pull request, inspect its current title and diff before proposing a name. Treat the title as a changelog entry for developers, not as a high-level summary of the work and not as an inventory of everything that changed. Do not automatically reuse the commit message.

Choose the narrowest title that still explains the developer-facing change. Aim for the right abstraction level rather than maximum specificity: use one concrete anchor and one clear outcome.

Choose the prefix

Do not infer the prefix from the directory name or from a Conventional Commit scope such as fix(core). For a package change, read the affected package's package.json and use its exact name value.

By default, use that package name in the PR title: