fix-dependabot

Update monorepo dependencies and lockfile for Dependabot pull requests.

57.9k|4.4k|Updated Jun 23, 2020
One-click install
npx skills add https://github.com/remotion-dev/remotion --skill fix-dependabot
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fix-dependabot
Source: https://github.com/remotion-dev/remotion/tree/main/.agents/skills/fix-dependabot
Command: npx skills add https://github.com/remotion-dev/remotion --skill fix-dependabot

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Dependabot pull requests only update a single package.json file and never run the package manager, leaving the lockfile out of sync and other monorepo packages referencing the old version. This Skill synchronizes all package.json files and regenerates the lockfile to keep the monorepo consistent.

Core Features & Use Cases

  • Monorepo-Wide Version Sync: Detects all package.json files referencing the old dependency version and updates them to the new version while preserving each package's existing version prefix style.
  • Lockfile Regeneration: Runs bun install from the repository root to regenerate bun.lock after version updates.
  • Verification and Commit: Confirms only expected files changed, commits the updates, and pushes the branch back to the remote.
  • Use Case: A Dependabot PR bumps vite from 5.4.0 to 6.0.0 in packages/player/package.json. Use this Skill to update the same dependency in packages/cli/package.json and packages/studio/package.json, regenerate bun.lock, and push the consolidated changes.

Quick Start

Use the fix-dependabot skill to update all monorepo package.json files and regenerate bun.lock for Dependabot PR number 1234.

Frequently Asked Questions about fix-dependabot

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I fix a Dependabot PR that only updates one package.json in a monorepo?

Checkout the Dependabot branch, use ripgrep to find all package.json files referencing the old version, update each match to the new version, then run bun install to regenerate bun.lock. Commit and push the changes back to the Dependabot branch.

Why does Dependabot leave the lockfile out of date in monorepos?

Dependabot only modifies the single package.json it targets and does not run the package manager. In monorepos, sibling packages still reference the old version and the lockfile becomes inconsistent until manually updated.

Can I use this workflow with npm or yarn instead of bun?

The skill is specifically written for bun install and bun.lock. For npm or yarn monorepos, replace the bun install step with the equivalent command for your package manager and adjust the lockfile verification accordingly.

What happens when a Dependabot PR is a major version bump?

Major version bumps may introduce breaking changes. The skill recommends reviewing the changelog and considering whether to merge, ignore the PR, or close it with an explanation if the upgrade conflicts with other packages.

How to handle bun install conflicts during a Dependabot update?

If bun install fails after updating all package.json files, the new version likely conflicts with peer dependencies in other packages. In that case, close the PR and comment explaining the conflict rather than forcing a merge.