Does this skill automatically change my main codebase?

No, the skill operates in an isolated Git worktree and requires your explicit approval at a decision point before any implementation begins. It concludes by submitting a Pull Request for human review.

How does it ensure the new library doesn't break my app?

The workflow uses a test-driven approach, verifying the refactored code against your existing test suite and adding new tests for edge cases handled by the library.

How does it choose which libraries to recommend?

It researches package registries to compare candidates based on popularity, maintenance frequency, bundle size impact, license compatibility, and API quality.

What types of custom code can it detect?

It scans for common patterns including date/time formatting, HTTP clients, schema validation, CLI parsing, logging, and complex string or data transformations.

Dependency Opportunity Scanner

Name: Dependency Opportunity Scanner
Author: samjhecht

bysamjhecht

•

Developer Tools

Identifies and replaces custom code implementations with well-maintained open-source libraries through an automated multi-phase workflow.

About

The Dependency Opportunity Scanner is a sophisticated workflow skill designed to reduce technical debt and maintenance burden by finding areas where custom code can be replaced with industry-standard libraries. It performs parallel analysis of your codebase to identify patterns like custom date manipulation or HTTP clients, researches the best-fit libraries based on maintenance and bundle size, and then automates the entire refactoring process—from creating a Git worktree to submitting a detailed Pull Request for human review.

Key Features

Parallel pattern detection for common custom utilities and helpers
1 GitHub stars
Test-driven refactoring to ensure functional parity with original code
Comprehensive PR generation with bundle size metrics and migration guides
Isolated implementation using Git worktrees to protect the main branch
Automated cost/benefit and impact analysis of library adoption

Use Cases

Standardizing codebase patterns across a large engineering team
Modernizing legacy codebases by replacing 'homegrown' utility functions
Reducing technical debt and long-term maintenance costs of custom logic

About

Key Features

Parallel pattern detection for common custom utilities and helpers
1 GitHub stars
Test-driven refactoring to ensure functional parity with original code
Comprehensive PR generation with bundle size metrics and migration guides
Isolated implementation using Git worktrees to protect the main branch
Automated cost/benefit and impact analysis of library adoption

Use Cases

Standardizing codebase patterns across a large engineering team
Modernizing legacy codebases by replacing 'homegrown' utility functions
Reducing technical debt and long-term maintenance costs of custom logic