dependency-opportunity-scanner

Identify custom code replacements with well-maintained open-source libraries.

4|1|Updated Oct 29, 2025
One-click install
npx skills add https://github.com/samjhecht/wrangler --skill dependency-opportunity-scanner
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dependency-opportunity-scanner
Source: https://github.com/samjhecht/wrangler/tree/main/skills/dependency-opportunity-scanner
Command: npx skills add https://github.com/samjhecht/wrangler --skill dependency-opportunity-scanner

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill coordinates a multi-phase workflow to identify opportunities to replace custom implementations with well-maintained open source libraries. It then implements changes in an isolated worktree and submits a PR for human review.

Core Features & Use Cases

  • Opportunity discovery: Parallel analysis identifies patterns ripe for library solutions.
  • Library research: Sequential evaluation of top candidates by popularity, maintenance, size, and API quality.
  • Implementation pipeline: Worktree-based refactor, tests, and PR creation for review.

Quick Start

Kick off the workflow to scan code for library opportunities, evaluate candidates, and prepare a PR-ready change set in a separate worktree.

Frequently Asked Questions about dependency-opportunity-scanner

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

FAQPage Schema
How do I identify opportunities to replace custom code with open-source libraries?

This Skill scans your codebase to find custom implementations that could be replaced with well-maintained open-source libraries. It uses parallel analysis to identify patterns, evaluates top library candidates by popularity and maintenance quality, then prepares a pull request with estimated LOC reductions and integration effort for your review.

Can I refactor dependencies without disrupting my main branch?

Yes. The Skill uses isolated worktrees to implement changes separately from your main codebase, runs tests to ensure coverage, and submits a pull request for human review before any merge. This ensures non-destructive refactoring with full auditability.

What makes a good candidate for library replacement?

The Skill evaluates candidates by maintenance status, popularity, API quality, and size. It prioritizes well-maintained libraries that reduce custom code significantly while remaining lightweight and fitting your existing tech stack.

How does the workflow handle multiple library candidates?

The Skill runs parallel analysis to identify patterns, then sequentially evaluates top candidates ranked by quality metrics. It produces actionable outputs including candidate libraries, LOC reductions, integration effort, and impact analysis so you can choose the best fit.

What output do I get from running this Skill?

You receive a pull request in a separate worktree containing refactored code, test coverage, candidate library details, estimated LOC savings, integration effort estimates, and rationale documentation—all ready for review before merging.