Complete a Dependabot update across a monorepo by updating matching dependency versions in other packages and regenerating bun.lock. Check the changed files, preserve existing version prefixes, then commit and push the fixes.
Fix a Dependabot PR by updating all monorepo instances of the dependency, running bun install, and pushing
Review the instructions the agent will receive before you install.
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.No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Add a reported Remotion bug to the bugs API with its affected versions, a short title, and upgrade guidance. Follow the existing entry format and place the new record first so recent bugs appear at the top.
Add a Remotion command-line or configuration option, or convert a hardcoded flag into a shared option definition. Connect parsing, configuration setters, help entries, and generated documentation so the option is consistently available and documented.
Add a new effect to @remotion/effects, including its implementation, package entry points, documentation, interactive demo, and preview images. Follow the package conventions and verify the changes with tests, formatting checks, and builds.
Add a person to the Remotion experts page by placing their portrait, entering their profile and contact links, and generating an expert card image. The instructions specify file locations, profile fields, and how to verify card generation.
Create a new @remotion package within the Remotion monorepo, a repository containing multiple packages. Set up its files, register it across the project, and prepare documentation, usage examples, and build configuration.
Add a new sound effect to @remotion/sfx, from registering the audio file to exporting its URL and documenting its use. The workflow covers playback examples, attribution, navigation entries, waveform generation, and the package build.