Pr Name Agent Skill
Review or correct a Remotion pull request title
Install
one command, takes just this skill from the repositorynpx skills add https://github.com/remotion-dev/remotion --skill pr-nameThe instruction itself
1 sections, as written by the authorWhen given a pull request, inspect its current title and diff before proposing a
name. Do not infer the prefix from the directory name or from a Conventional
Commit scope such as fix(core). Read the affected package's package.json and
use its exact name value.
By default, use that package name in the PR title:
`[package-name]`: [commit-message]
For example:
`@remotion/shapes`: Add heart shape
If multiple packages are affected, use the one that you think is most relevant.
Special handling
For changes that match one of the categories below, use its special prefix instead of a package name. Classify the change by its user-facing impact, not merely by the package directory containing the changed files.
If a change only adds, fixes, or stabilizes internal tests, test fixtures, snapshots, or test infrastructure, and does not change shipped behavior, use the Internal: prefix. This also applies to package-local tests under a published package. Do not use that package's name as the prefix just because the test is located there. The package name may instead appear in the description when useful:
Internal: Stabilize registration range test in `@remotion/transitions`
If shipped implementation changes are accompanied by tests, use the normal affected-package prefix instead.
If the change is about docs only:
Docs: Add page about heart shape
If the change is internal monorepo work that does not have a more specific
category below, use the Internal: prefix:
Internal: Simplify release bookkeeping
If the change relates to Remotion Elements, use the Elements: prefix:
Elements: Add animated title element
If the change relates to packages/convert, use the remotion.dev/convert prefix:
remotion.dev/convert: Support trimming
If the change relates to packages/example, say Internal Testbed:
Internal testbed: Add trimming sample composition
If the change adds or modifies a skill, prefix with Skills::
Skills: Add `/remotion-upgrade` skill
If the change relates to packages/brand, prefix with remotion.dev/brand:
remotion.dev/brand: Add animated logo
If the change relates to packages/it-tests, prefix with Internal tests:
Internal tests: Add video integration test
Other skills for the same job
different authors, same section of the catalogue
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
Execute git commit with conventional commit message analysis, intelligent staging, and message generation. Use when user asks to commit changes, create a git commit, or mentions "/commit". Supports: (1) Auto-detecting type and scope from changes, (2) Generating conventional commit messages from diff, (3) Interactive commit with optional type/scope/description overrides, (4) Intelligent file staging for logical grouping
Comprehensive GitHub code review with AI-powered swarm coordination
Behavioral guidelines to reduce common LLM coding mistakes. Use when writing, reviewing, or refactoring code to avoid overcomplication, make surgical changes, surface assumptions, and define verifiable success criteria.
Use this skill to review code. It supports both local changes (staged or working tree) and remote Pull Requests (by ID or URL). It focuses on correctness, maintainability, and adherence to project standards.
Refactor bloated AGENTS.md, CLAUDE.md, or similar agent instruction files to follow progressive disclosure principles. Splits monolithic files into organized, linked documentation.
Create high-quality git commits: review/stage intended changes, split into logical commits, and write clear commit messages (including Conventional Commits). Use when the user asks to commit, craft a commit message, stage changes, or split work into multiple commits.
How to use it
Take remotion-dev/pr-name from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.