Correct naming for a PR
56
62%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Passed
No findings from the security scan
Fix and improve this skill with Tessl
tessl review fix ./.agents/skills/pr-name/SKILL.mdBy default, use the affected package name from its package.json in the PR title:
`[package-name]`: [commit-message]For example:
`@remotion/shapes`: Add heart shapeIf multiple packages are affected, use the one that you think is most relevant.
For changes that match one of the categories below, use its special prefix instead of a package name.
If the change is about docs only:
Docs: Add page about heart shapeIf the change adds or modifies a skill, or is otherwise internal monorepo work, use the Internal prefix:
Internal: Add PR naming skillIf the change relates to Remotion Elements, use the Elements: prefix:
Elements: Add animated title elementIf the change relates to packages/convert, use the remotion.dev/convert prefix:
remotion.dev/convert: Support trimmingIf the change relates to packages/example, say Internal Testbed:
Internal testbed: Add trimming sample compositionIf the change relates to Skills, prefix with Skills:
Skills: Add `/remotion-upgrade` skillIf the change relates to packages/brand, prefix with remotion.dev/brand:
remotion.dev/brand: Add animated logoIf the change relates to packages/it-tests, prefix with Internal tests:
Internal tests: Add video integration test1b58387
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.