Agent skill · writing content · remotion-dev
pr-name
Review or correct a Remotion pull request title
Why this skill is useful
Provides specific naming conventions and prefixes for pull request titles based on package changes, which the AI wouldn't reliably generate on its own.
What it needs
About 3k tokens when loaded. Last updated 2026-08-06. 55,698 stars on the source repository.
What this skill does
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: For example: If multiple packages are affected, use the package that owns the primary user-facing change, not necessarily the package with the most changed files. Describe the change Use these guidelines in order: 1. Identify the main developer-visible change from the diff. 2. If a public API is central to the change, name the primary API exactly in backticks and briefly explain what it does. Do not list supporting APIs. 3. Otherwise, describe what changed rather than the files or implementation steps used to achieve it. Include technical details only when they help developers understand the result. Prefer concrete verbs such as add, fix, remove, rename, and change. Avoid vague descriptions such as allow, improve, update handling, or support when the diff provides a clearer description. PR titles may use concise, telegraphic wording. Do not add articles or filler solely to make the title a grammatically complete sentence; keep them when they improve clarity. Useful title shapes include: Examples: The first example is better than "Add libraries to Studio" because it names the main API and explains its purpose. The Studio CSS example deliberately describes the visible result instead of the CSS file or overflow rule that implemented it. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills remotion-dev/pr-name