skills.rest
remotion-dev
remotion-devOFFICIAL
Explore all skills by this author →
Website𝕏@remotionGitHub

pr-name

Review and propose Remotion pull request titles following package-prefix conventions.

57.9k|4.4k|Updated Jun 23, 2020
Search Tags:#naming conventions#Monorepo#gitHub#Remotion#Code review#Pull request#ChangeLog
One-click install
npx skills add https://github.com/remotion-dev/remotion --skill pr-name
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pr-name
Source: https://github.com/remotion-dev/remotion/tree/main/.agents/skills/pr-name
Command: npx skills add https://github.com/remotion-dev/remotion --skill pr-name

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Writing a clear, consistent pull request title for a Remotion change is hard because the title must read like a developer-facing changelog entry, use the correct package prefix from package.json, and avoid vague verbs. This Skill inspects the PR diff and current title to propose a precise, conventional title.

Core Features & Use Cases

  • Package Prefix Selection: Reads the affected package's package.json to derive the exact prefix, or applies special prefixes like Internal:, Docs:, Elements:, or Skills: based on change category.
  • Title Crafting Guidelines: Recommends concrete verbs (add, fix, remove, rename, change) and telegraphic wording, naming the primary API in backticks when relevant.
  • Use Case: A contributor opens a PR that adds a metadata option to renderMediaOnWeb() in @remotion/web-renderer. Use this Skill to produce the title @remotion/web-renderer: Add a metadata option to renderMediaOnWeb() using Mediabunny's MetadataTags.

Quick Start

Review the current pull request title and diff, then propose a corrected title following the package-prefix and verb conventions.

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 good pull request title for Remotion?▼

Use the affected package's exact `name` from its `package.json` as the prefix, followed by a concrete verb like `add`, `fix`, or `remove`. Name the primary API in backticks and keep the wording telegraphic without filler articles.

What prefix should I use for Remotion PR titles?▼

Use the package name from `package.json` for shipped changes. Use `Internal:` for test-only or monorepo work, `Docs:` for documentation, `Elements:` for Remotion Elements, and `Skills:` for skill additions or modifications.

Can I reuse the commit message as the PR title?▼

No. The PR title should be treated as a changelog entry for developers, not as a commit message. Choose the narrowest title that explains the developer-facing change at the right abstraction level.

Why are vague verbs like 'improve' or 'support' discouraged?▼

Vague verbs do not describe the observable developer-facing change. Concrete verbs such as `add`, `fix`, `remove`, `rename`, and `change` communicate the actual outcome and make changelogs scannable.

When should I use the Internal prefix instead of a package name?▼

Use `Internal:` when the change only adds, fixes, or stabilizes tests, fixtures, snapshots, or test infrastructure without altering shipped behavior. Shipped implementation changes should use the normal affected-package prefix even when accompanied by tests.

Related Skills

Explore More Software Engineering Skills→
remotion-devremotion-dev
55.9k

make-pr

Create a pull request for affected packages using the GitHub CLI.

Official
Advanced
andreciniandrecini
2

write-changelog-entry

Generate a new CHANGELOG.md release entry from merged pull requests and commits.

Community
Intermediate
ElbertePlinioElbertePlinio

create-pr

Generate Conventional Commits PR titles, templated bodies, and run local checks.

Community
Intermediate
punkfuncgamespunkfuncgames

conventional-commits

Standardize git commit messages using the Conventional Commits format.

Official
Basic