Dependency Management

aj-geddes/useful-ai-prompts/skills/dependency-management

by aj-geddes3f5182cfd739No license355 starsListed Oct 8, 2026Updated Oct 8, 2026Repository updated 7 months ago

Manage project dependencies across languages including npm install, package versioning, dependency conflicts, security scanning, and lock files. Use when dealing with dependencies, version pinning, semantic versioning, or resolving conflicts.

AI-generated overview

Guides dependency management across ecosystems: installs, versioning, lock files, conflicts, and security audits.

What it does
This skill provides guidance and reference material for managing project dependencies in JavaScript/Node.js, Python, Ruby, Java and other ecosystems. It covers installing and updating packages, semantic versioning, lock files, resolving version conflicts, peer dependencies, monorepo setups, performance optimization, CI/CD practices, and security vulnerability auditing. It also ships a test scaffolding script and a test template, plus ten reference guides in a references directory.
When to use it
Use it when installing or updating dependencies, resolving version conflicts, auditing vulnerabilities, managing lock files, applying semantic versioning, or setting up monorepo and peer dependency structures. It is also relevant when optimizing dependency trees or defining dependency update strategies.
Requirements
Runs in an agent with access to the skill's reference files. The bundled scripts/scaffold-tests.sh and templates/test-template.js require a shell environment; package manager commands such as npm are described but not bundled.

Dependency Management

Table of Contents

Overview

Comprehensive dependency management across JavaScript/Node.js, Python, Ruby, Java, and other ecosystems. Covers version control, conflict resolution, security auditing, and best practices for maintaining healthy dependencies.

When to Use

  • Installing or updating project dependencies
  • Resolving version conflicts
  • Auditing security vulnerabilities
  • Managing lock files (package-lock.json, Gemfile.lock, etc.)
  • Implementing semantic versioning
  • Setting up monorepo dependencies
  • Optimizing dependency trees
  • Managing peer dependencies

Quick Start

Minimal working example:

bash
# Initialize projectnpm init -y
# Install dependenciesnpm install expressnpm install --save-dev jestnpm install --save-exact lodash  # Exact version
# Update dependenciesnpm updatenpm outdated  # Check for outdated packages
# Audit securitynpm auditnpm audit fix
# Clean install from lock filenpm ci  # Use in CI/CD
# View dependency treenpm listnpm list --depth=0  # Top-level only

Reference Guides

Detailed implementations in the references/ directory:

GuideContents
Package Manager Basics [blocked]Package Manager Basics
Semantic Versioning (SemVer) [blocked]Semantic Versioning (SemVer)
Dependency Lock Files [blocked]Dependency Lock Files
Resolving Dependency Conflicts [blocked]Resolving Dependency Conflicts
Security Vulnerability Management [blocked]Security Vulnerability Management
Monorepo Dependency Management [blocked]Monorepo Dependency Management
Peer Dependencies [blocked]Peer Dependencies
Performance Optimization [blocked]Performance Optimization
CI/CD Best Practices [blocked]CI/CD Best Practices
Dependency Update Strategies [blocked]Dependency Update Strategies

Best Practices

✅ DO

  • Commit lock files to version control
  • Use npm ci or equivalent in CI/CD pipelines
  • Regular dependency audits (weekly/monthly)
  • Keep dependencies up-to-date (automate with Dependabot)
  • Use exact versions for critical dependencies
  • Document why specific versions are pinned
  • Test after updating dependencies
  • Use semantic versioning correctly
  • Minimize dependency count
  • Review dependency licenses

❌ DON'T

  • Manually edit lock files
  • Mix package managers (npm + yarn in same project)
  • Use npm install in CI/CD (use npm ci)
  • Ignore security vulnerabilities
  • Use wildcards (*) for versions
  • Install packages globally when local install is possible
  • Commit node_modules to git
  • Use latest tag in production
  • Blindly run npm audit fix
  • Install unnecessary dependencies

Source and attribution

Source:aj-geddes/useful-ai-promptsinskills/dependency-managementat commit3f5182c

License: No license

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal