Pr Name
Format pull request titles correctly when contributing to a Remotion-style monorepo so reviewers and release tooling can scan changes by package.
Install
npx skills add https://github.com/remotion-dev/remotion --skill pr-nameWhat is this skill?
- Enforces `` `package-name`: commit message `` using the name from package.json
- Uses Docs: prefix when the change is documentation-only
- Picks the most relevant package when multiple packages are touched
- Includes concrete example: `@remotion/shapes`: Add heart shape
Adoption & trust: 298 installs on skills.sh; 49.4k GitHub stars; 3/3 security scanners passed (skills.sh audits).
Recommended Skills
Triagemattpocock/skills
Caveman Commitjuliusbrussee/caveman
Using Git Worktreesobra/superpowers
Finishing A Development Branchobra/superpowers
Git Commitgithub/awesome-copilot
Git Guardrails Claude Codemattpocock/skills
Journey fit
Primary fit
PR title conventions are applied right before merge and during code review, which maps to the Ship phase when changes leave your branch. Review is where naming discipline matters most—titles are read in PR lists, CI, and changelog automation during review.
Common Questions / FAQ
Is Pr Name safe to install?
skills.sh reports 3 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.
SKILL.md
READMESKILL.md - Pr Name
The following format must be used for the PR title: ``` `[package-name]`: [commit-message] ``` For example: ``` `@remotion/shapes`: Add heart shape ``` The package name must be obtained from package.json. If multiple packages are affected, use the one that you think if most relevant. If the change is about docs only: ``` Docs: Add page about heart shape ```