BastiDood

Dependency Wrangler — Development skill for Claude Code

Development community

A Claude Code marketplace for plugins that wrangle your dependencies.

How to install Dependency Wrangler

This entry records only its repository, not the path inside it, so there is no exact command to give. Open BastiDood/dependency-wrangler and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Dependency Wrangler does

A Claude Code marketplace for plugins that wrangle your dependencies.

Alternatives in Development

Epic Unblock — Sweep blocked epic issues and reopen anything whose dependencies are closed 243.5k ★
Sanitize — Detect and redact PII from text files — 15 categories (SSNs, credit cards, API keys, etc.), zero dependencies 3.1k ★
Open Agent SDK TypeScript — Agent-SDK without CLI dependencies, as an alternative to claude-agent-sdk, completely open source 2.6k ★

README

Dependency Wrangler

A [Claude Code](https://code.claude.com/docs/en/overview) plugin marketplace for dependency management tools.

Installation

/plugin marketplace add bastidood/dependency-wrangler
/plugin install dependabump@dependency-wrangler

Plugins

Dependabump

Orchestrates dependency bumping across package managers: `npm`, `pnpm`, `yarn`, `bun`, `uv`, and `cargo`.

/dependabump:bump-dependencies

Flag	Effect
`--include-major`	Include major version bumps (deferred by default)
`--include-patch`	Analyze patch bumps (assumed safe by default)

The workflow detects outdated packages, scrapes changelogs, assesses codebase impact, and proposes a staged upgrade plan ordered from safest to riskiest.

[!WARNING] Running this workflow across ~20 dependencies can consume up to half of the 5-hour rate limits in a $100 Claude Max subscription. With ~40 parallelized dependencies, you may even hit rate limits on a single run entirely.

This is why the `--include-major` and `--include-patch` flags are disabled by default. Typically, most unexpected breaking changes occur in minor version bumps anyway.

But, it's still better to _not_ be in this situation in the first place. **When it comes to dependency management, it's far easier to keep up than catch up.**

flowchart TD
    orchestrator["/dependabump:bump-dependencies"] --> finder

    finder["Dependency Finder
    (Haiku)"]
    finder -- outdated list --> fan_out

    fan_out{"Fan-out per Package"}
    fan_out -- "pkg-1" --> scraper_1["Changelog Scraper
    (Sonnet)"]
    fan_out -- "pkg-2" --> scraper_2["Changelog Scraper
    (Sonnet)"]
    fan_out -- "pkg-N" --> scraper_n["Changelog Scraper
    (Sonnet)"]
    scraper_1 --> join{Join}
    scraper_2 --> join
    scraper_n --> join

    join -- ch