agentleFS
Sign inStart free
saitarrunsaitarrun/Devforge-ai/skills/dependency-management/SKILL.md

dependency-management

Skill4 starsChanged 5 months agoApache-2.0View on GitHub

Version updates (major/minor/patch), security patch application, transitive dependency resolution, monorepo dependency management, deprecation tracking, license compliance. Use when updating dependencies, managing versions, or addressing CVEs.

18 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use infrastructure-as-code, release-management and 7 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • mmondoraSkill

    infrastructure-as-code

    Infrastructure as Code with Terraform and Pulumi. State management, modularity, drift detection, secrets handling. Use when provisioning cloud resources, writing Terraform/Pulumi modules, or managing infrastructure configuration.

    Also in 4 projects that use this

  • Microsoft AzureSkill

    release-management

    Prepares and validates AI Landing Zone semantic releases. Use for changelog entries, manifest versions, release branches, tags, GitHub Releases, and post-release branch reconciliation.

    Also in 4 projects that use this

  • MicrosoftSkill

    deployment

    Also in 3 projects that use this

  • wrsmith108Skill

    docker

    Container-based development for isolated, reproducible environments. Use when running npm commands, installing packages, executing code, or managing project dependencies. Trigger phrases include "npm install", "run the build", "start the server", "install package", or any code execution request.

    Also in 3 projects that use this

  • Microsoft AzureSkill

    git-workflow

    Squad branching model: dev-first workflow with insiders preview channel

    Also in 7 projects that use this

  • pproencaSkill

    refactoring

    Code refactoring best practices based on Martin Fowler's catalog and Clean Code principles. This skill should be used when refactoring existing code, improving code structure, reducing complexity, eliminating code smells, or reviewing code for maintainability. Triggers on tasks involving extract method, rename, decompose conditional, reduce coupling, or improve readability.

    Also in 3 projects that use this

The file

Create a free account to mount
Files
SKILL.md

Skill: Dependency Management

Stay current. Stay secure. Minimize version mismatch.

Version Updates

Semantic Versioning:

  • 1.0.0 → 2.0.0: Breaking change (test, update code)
  • 1.0.0 → 1.1.0: New feature (backward-compatible, usually safe)
  • 1.0.0 → 1.0.1: Bug fix (safe to update)

Security Patch Strategy

# 1. Check for vulnerabilities
npm audit  # or pip check, cargo audit

# 2. Update vulnerable packages
npm update lodash@4.17.21

# 3. Test changes
npm test

# 4. Commit & push
git commit -m "fix(deps): update lodash to patch CVE-2021-23337"

Transitive Dependency Hell

app → requests@2.28.0
app → urllib3@1.26.0
app → certifi@2022.9.24

requests → urllib3@1.25.0  # Different version!

Solution: Lock files (requirements.txt, package-lock.json, Cargo.lock)

Monorepo Dependencies

Shared dependencies (lock once):

root/
  Cargo.lock  # All crates use this
  crates/
    auth/
    api/
    db/

Deprecation Tracking

# Checklist when you deprecate something
- [ ] Announce (email, docs, header warning)
- [ ] Timeline (6 months warning)
- [ ] Alternatives (what should users use?)
- [ ] Test (ensure new way works)
- [ ] Remove (after timeline)

Status: Ready for dependency work
Best for: Version updates, security patches, CVE management

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free