skills.rest
EmeaAppGbb
EmeaAppGbbOFFICIAL
Explore all skills by this author →
GitHub

dependency-inventory

Identify and document project dependencies, versions, and purposes from manifests and lock files.

Updated Mar 30, 2026
Search Tags:#versioning#dependency management#dependency mapping#software analysis#dependency inventory
One-click install
npx skills add https://github.com/EmeaAppGbb/spec2cloud-microhack-greenfield --skill dependency-inventory
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dependency-inventory
Source: https://github.com/EmeaAppGbb/spec2cloud-microhack-greenfield/tree/main/.github/skills/dependency-inventory
Command: npx skills add https://github.com/EmeaAppGbb/spec2cloud-microhack-greenfield --skill dependency-inventory

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Dependency Inventory solves the problem of maintaining an up-to-date and comprehensive list of all dependencies in a software project, including their versions, purposes, and relationships.

Core Features & Use Cases

  • Comprehensive Dependency Mapping: Automatically scans and maps all direct and transitive dependencies.
  • Version Detailing: Provides exact version constraints and resolved versions from lock files.
  • Dependency Purpose Identification: Determines the purpose of each dependency based on package names, codebase usage, and descriptions.
  • Versioning Strategy Analysis: Documents the versioning strategies used in the project, including exact pinning and range usage.

Quick Start

Run the dependency-inventory skill in the project root to generate a complete inventory of dependencies in 'specs/docs/technology/dependencies.md'.

Frequently Asked Questions about dependency-inventory

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

FAQPage Schema
How do I generate a comprehensive dependency inventory for my software project?▼

A dependency inventory identifies and documents all dependencies, versions, and purposes in a software project by analyzing package manifests, lock files, and the codebase to map direct and transitive relationships.

What's the best way to map direct and transitive dependencies along with their version constraints?▼

Mapping direct and transitive dependencies is best handled by scanning lock files and package manifests to extract exact version constraints, resolved versions, and dependency relationships for comprehensive project documentation.

Do I need package manifests and lock files to analyze versioning strategies and dependency purposes?▼

Yes, you need access to package manifests, lock files, and the project's codebase to accurately determine dependency purposes, document versioning strategies, and report on exact pinning and range usage.

Can I document dependency purposes and relationships by analyzing the codebase?▼

Yes, you can document dependency purposes by analyzing package names, codebase usage, and descriptions, which allows the skill to determine the specific role of each dependency within the software project.

How does version detailing work when inventorying software dependencies?▼

Version detailing works by reading lock files to provide exact resolved versions and checking package manifests for version constraints, ensuring the dependency inventory accurately reflects your current software environment.

Related Skills

Explore More Software Engineering Skills→
crgarcia12crgarcia12

dependency-inventory

Extract and catalog project dependencies from package manifests and lock files.

Community
Advanced
ActiveInferenceInstituteActiveInferenceInstitute
30

gnn-security-validation

Audit GNN pipeline security and validate access control for generated code.

Community
Advanced
strawgatestrawgate

find-stale-issues

Identify stale, resolved, or duplicate GitHub issues via semantic similarity analysis.

Community
Advanced
dandudzidandudzi
2

ddd-strategic-design

Map business domains and define bounded contexts with DDD strategic patterns.

Community
Advanced