dependency-search
Installation
SKILL.md
Use this skill to research $ARGUMENTS across all available repositories when the question is about dependency usage, dependency ownership, upgrade planning, migration scope, version drift, or remediation.
Use cases for dependency search
- Find where a dependency is used. Locate repos importing a package, requiring a module, referencing a framework, or declaring a dependency in package manifests, lockfiles, build files, Dockerfiles, or infrastructure config.
- Plan dependency upgrades. Identify consumers, pinned versions, compatibility wrappers, tests, and release paths before upgrading a shared package, runtime, SDK, framework, or generated client.
- Scope CVE and security remediation. Find vulnerable package versions, transitive dependency clues, vendored copies, or repeated mitigation patterns across repos.
- Discover dependency owners and migration examples. Find the repos that maintain a shared package and the repos that have already migrated to a newer API or replacement dependency.
- Compare version drift. Search for multiple declared versions or config variants to decide whether the org has one canonical version, several legacy versions, or repo-specific exceptions.
- Find imports that do not appear in manifests. Search for runtime imports, generated imports, plugin names, package namespaces, or error strings when manifest searches are incomplete.
- Trace shared client and SDK usage. Locate services using a generated API client, database library, observability package, authentication SDK, feature flag SDK, or common internal library.
- Prepare deprecations and removals. Identify remaining consumers, compatibility layers, fallback code, and tests that would be affected by removing a dependency.
- Audit dependency configuration. Search build systems, CI workflows, package managers, container images, Terraform modules, Helm charts, and language-specific dependency files for risky or inconsistent configuration.
Workflow
- Find candidate repositories first. Run the experimental repo discovery command before searching code: