Menu
Fix a Dependabot PR by updating all monorepo instances of the dependency, running bun install, and pushing
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Add a new effect to @remotion/effects, including implementation, package exports, docs, demos, preview images, Remotion skill updates, tests, formatting, and builds.
Add a new sound effect to @remotion/sfx
Publish Remotion Lambda Chrome binaries to the eu-central-1 test region and update hosted layer and Chrome version references. Use when updating Chrome binaries before full regional rollout.
Document Remotion skill placement. Use when adding, moving, or editing Remotion skills to decide whether a skill belongs in .agents/skills as an internal skill or packages/skills as a public skill.
Guidance for Remotion Studio UI changes where the global CSS reset affects nested elements. Use when editing packages/studio UI, especially when adding wrapper spans, inline icons, labels, buttons, compact rows, or any nested text whose typography, color, sizing, or truncation must stay stable.
Start Remotion Studio from packages/example and open it in the Codex browser. Use when the user invokes /studio or $studio, asks to launch the example Studio, or wants the Remotion Studio dev UI available locally.
Based on SOC occupation classification
| name | fix-dependabot |
| description | Fix a Dependabot PR by updating all monorepo instances of the dependency, running bun install, and pushing |
Dependabot PRs only update one package.json and never run bun install, so the bun.lock file is out of date and other packages in the monorepo still reference the old version. This skill fixes both problems.
Get PR info — Use gh pr view <number> --json headRefName,files,title,body to identify the branch name, which dependency was bumped, and the old/new versions.
Checkout the branch:
git fetch origin <branch>
git checkout <branch>
package.json files that reference the same dependency at the old version and update them too:rg '"<dependency>": "[~^]?<old-version>"' --glob '**/package.json'
Update every match to the new version. Preserve the prefix style (^, ~, or exact) that each package already uses.
Run bun install from the repo root to regenerate bun.lock.
Verify — Run git status to confirm only bun.lock and the expected package.json files were modified. If other unexpected files changed, investigate before proceeding.
Commit and push:
git add -u
git commit -m "Update <dependency> to <version> across all monorepo packages"
git push
main):git checkout main
bun install fails, the dependency version may have conflicts with other packages. In that case, close the PR and comment explaining why.