dependency-audit

Audit project dependencies and categorize outdated packages into risk tiers.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Dependency updates are error-prone and time-consuming for engineering teams. This skill inventories outdated packages, categorizes them into risk-based tiers, and generates a read-only decision report to guide upgrades without modifying manifests or lockfiles.

Core Features & Use Cases

  • Inventory outdated dependencies and classify them into Tier A (safe patch/minor), Tier B (non-core major), and Tier C (core/risky) based on changelogs and runtime impact.
  • Fetch breaking-change notes from package changelogs, grep the codebase for consumed APIs, and verify test baselines to assess impact.
  • Deliver a read-only decision report and runtime compatibility checks to help teams plan upgrades with minimal risk.

Quick Start

Run the audit on your project to inventory outdated dependencies and generate a risk-based upgrade plan.

Frequently Asked Questions about dependency-audit

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

FAQPage Schema
How do I audit outdated dependencies to identify breaking changes and risk?

This skill inventories outdated dependencies and classifies them into Tier A, B, or C based on risk. It fetches breaking changes from changelogs, greps the codebase for suspected API usage, and validates test baselines to assess impact.

What is the safest way to categorize dependency updates for a large codebase?

Categorize dependency updates by classifying packages into Tier A (safe patch/minor), Tier B (non-core major), and Tier C (core/risky) based on changelogs, codebase API usage, and runtime compatibility checks against current LTS.

Does the dependency audit modify my project manifest or lockfiles?

No, the dependency audit is strictly read-only and does not modify any manifest or lockfiles. It produces a decision report and checks runtime compatibility against current LTS to help you plan safe upgrades.

Can I apply stack-aware rules when auditing dependencies for node, python, or swift?

Yes, you can apply stack-aware rules for node, python, or swift dependencies when a PATTERNS.md file is present in your project, allowing the audit to tailor its risk assessment to your specific stack.

What are the limitations of using an automated dependency audit report?

The limitation of this dependency audit is that it cannot automatically apply updates or modify manifests. It only provides a read-only decision report and runtime compatibility checks to guide manual upgrade planning.