Skip to main content
Agent skill

Fix Dependabot

Fix a Dependabot PR by updating all monorepo instances of the dependency, running bun install, and pushing

Get started

Get the complete skill folder, including its scripts and reference files.

When to use this skill

Use Fix Dependabot when an AI agent needs a reusable SKILL.md workflow for this job: Fix a Dependabot PR by updating all monorepo instances of the dependency, running bun install, and pushing

When not to use it

Skip Fix Dependabot when the task is outside the coding category, or when a more specific skill in this directory already covers the same workflow with clearer triggers.

How to install

Where will you use it?

Install scope
Claude Code folder setup
mkdir -p ~/.claude/skills/fix-dependabot
# Save SKILL.md to ~/.claude/skills/fix-dependabot/SKILL.md
  1. Claude Code personal install: place the skill and its bundled files at ~/.claude/skills/fix-dependabot/SKILL.md. For a shared project, commit the folder at .claude/skills/fix-dependabot/ instead.
  2. Current Claude Code detects SKILL.md changes in watched directories during the session. If you just created a top-level skills directory, run /reload-skills. Check that the skill is listed before testing its trigger.
  3. For Claude chat or Cowork in the Desktop app, manage uploaded skills in Customize > Skills; copying files into a local Claude Code folder is not a Desktop install. Other agents may use different install locations.

Full install guide for Claude, Cursor, and Codex →

Try a starter prompt

After installing the skill, paste this starter prompt into your agent to verify it triggers on a small task.

Starter prompt
Use the Fix Dependabot skill for this task: Use Fix Dependabot when this documented workflow matches the task. Confirm any required inputs or files before making changes.

What supports this recommendation?

68/100 provisional content score. This measures documentation, practical detail and source signals. It is not a measured task success rate or a security certification.

Documentation
70/100
Practical detail
68/100
Source evidence
63/100
Source signals
70/100
Model compatibility evidence
  • claudeuntested

    No model-specific signal or recorded compatibility test was found.

  • chatgptuntested

    No model-specific signal or recorded compatibility test was found.

  • geminiuntested

    No model-specific signal or recorded compatibility test was found.

  • copilotuntested

    No model-specific signal or recorded compatibility test was found.

  • llamauntested

    No model-specific signal or recorded compatibility test was found.

  • perplexityuntested

    No model-specific signal or recorded compatibility test was found.

  • mistraluntested

    No model-specific signal or recorded compatibility test was found.

  • grokuntested

    No model-specific signal or recorded compatibility test was found.

Inferred compatibility is based on content signals. Check the app, its available tools and setup requirements before running a skill.

What this skill does

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.

## Steps

1. **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.

2. **Checkout the branch**:

```bash git fetch origin <branch> git checkout <branch> ```

3. **Update all monorepo instances** — Dependabot only touches one package. Search for all other `package.json` files that reference the same dependency at the old version and update them too:

```bash 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.

4. **Run `bun install`** from the repo root to regenerate `bun.lock`.

5. **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.

6. **Commit and push**:

```bash git add -u git commit -m "Update <dependency> to <version> across all monorepo packages" git push ```

7. **Switch back** — Return to your previous branch (usually `main`):

```bash git checkout main ```

## Notes

- Dependabot says "Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself" — but updating the lockfile and sibling packages is the expected workflow and won't cause issues. - If the version bump is a major version (e.g. vite 5 → 6), consider whether the upgrade is appropriate or if it should be ignored. Check for breaking changes. - If `bun install` fails, the dependency version may have conflicts with other packages. In that case, close the PR and comment explaining why.

Intended uses

  • Use Fix Dependabot when this documented workflow matches the task.

Implementation notes

  • Review the source instructions and adapt inputs before running the workflow.

Try it, then tell us how it went

A copied prompt does not tell us whether the task worked. Report your result after checking the output. We collect your tool and outcome, never your files or prompt.