dependency-scan

Scan codebases to identify dependency usage with file paths and line numbers.

3|Updated Mar 17, 2026
One-click install
npx skills add https://github.com/marcoguillermaz/claude-dev-kit --skill dependency-scan-marcoguillermaz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dependency-scan
Source: https://github.com/marcoguillermaz/claude-dev-kit/tree/main/packages/cli/templates/tier-m/.claude/skills/dependency-scan
Command: npx skills add https://github.com/marcoguillermaz/claude-dev-kit --skill dependency-scan-marcoguillermaz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams quickly audit all dependency references across a codebase to surface cross-cutting usage and potential coupling.

Core Features & Use Cases

  • Six checks in one run: routes, components, shared types/utilities, test references, foreign keys, and access policies.
  • Structured reports with file paths and line numbers for each finding.
  • Use case: Before refactoring a module, run the scan to map all impacted areas and references.

Quick Start

Run the dependency-scan to produce a comprehensive usage report for the affected entities.

Frequently Asked Questions about dependency-scan

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

FAQPage Schema
How do I audit all dependency references in a codebase before refactoring?

To audit dependency references before refactoring, run a static analysis scan across your codebase to map all impacted areas. This generates a structured report with exact file paths and line numbers for every usage finding.

What does a static codebase dependency scan include?

A static codebase dependency scan includes six checks in one run: routes, components, shared types and utilities, test references, database foreign keys, and access control policies.

Can I trace database foreign keys and access policies during a dependency scan?

Yes, you can trace database foreign keys and access control policies during a dependency scan. The scan applies static analysis to these specific areas to identify cross-cutting usage and potential coupling.

How do I find exact file paths and line numbers for shared type references?

To find exact file paths and line numbers for shared type references, execute a static analysis scan. It produces a structured report detailing precise locations for every dependency usage across the codebase.

What is the best way to map cross-cutting component usage across a codebase?

The best way to map cross-cutting component usage is a one-pass dependency audit. It surfaces all references and potential coupling by performing static analysis to produce a comprehensive structured report.