agentleFS
SwastikPandey1024SwastikPandey1024/agentic-engineering-os/.agents/skills/dependency-management/SKILL.md

dependency-management

Skill1 starsChanged 3 months agoMITView on GitHub

Safe addition, pinning, upgrading, and conflict diagnosis for Python and JavaScript dependencies without version thrashing.

  • Installs packages

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 4 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

  • 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

  • shanggqmSkill

    data-analysis

    数据分析技能,提供结构化的数据查询、统计分析和报告生成工作流。当用户需要查询数据库、进行数据统计分析、生成分析报告时使用。按规范输出原始数据、计算结果、Markdown报告和HTML可视化报告。

    Also in 3 projects that use this

  • 0xSeroSkill

    security

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

7 rules. 0 are common, 1 is distinctive, and 6 are very specific to this project.

  • 0

    Common

    Most of the 17 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 6

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill when:

    line 10
  2. Very specific:

    Do NOT use this skill for initial environment bootstrapping (use python-environment).

    line 16
  3. Very specific:

    Check if the desired library is already pulled in as a sub-dependency (uv pip tree or npm ls <pkg>).

    line 26
  4. Very specific:

    Runtime Compatibility: Check current Python version (e.g.

    line 27
  5. Very specific:

    NEVER add unpinned unbounded dependencies: Avoid bare package names with no constraints (requests vs requests>=2.31.0,<3.0.0).

    line 107
  6. Very specific:

    NEVER edit uv.lock or package-lock.json manually: Always let the package manager generate the lockfile.

    line 108
  7. Very specific:

    NEVER use multiple package managers in the same project: Avoid mixing pip, poetry, and conda concurrently in a single repo.

    line 109

“Common” is measured: kept by at least 6 in 10 of the 17 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Dependency Management Skill

1. When Should I Use This?

Use this skill when:

  • Adding a new third-party library to a Python or JavaScript project.
  • Resolving package version conflicts or peer dependency errors (pip, uv, npm, pnpm).
  • Upgrading existing dependencies safely.
  • Distinguishing between runtime dependencies and development/test dependencies.

Do NOT use this skill for initial environment bootstrapping (use python-environment).


2. What Should I Inspect First?

  1. Manifest Files:
    • Python: pyproject.toml, requirements.txt, requirements-dev.txt, uv.lock, poetry.lock.
    • Node: package.json, package-lock.json.
  2. Current Constraints & Transitive Trees:
    • Check if the desired library is already pulled in as a sub-dependency (uv pip tree or npm ls <pkg>).
  3. Runtime Compatibility: Check current Python version (e.g. 3.11 vs 3.12) or Node engine version before selecting packages with strict C-extensions or compilation requirements (e.g. pydantic-core, paddlepaddle, faiss-cpu, tensorflow).

3. What Workflow Should I Follow?

Inspect Manifest & Lockfile
           ↓
Check if package already exists indirectly
           ↓
Determine Compatibility with Python / Node version
           ↓
Make the SMALLEST safe change in manifest
           ↓
Update Lockfile (uv lock / npm install)
           ↓
Run Import / Smoke Test Checks
           ↓
Run Full Test Suite to Catch Breaking Changes

Python Dependency Protocol (pyproject.toml)

# pyproject.toml
[project]
name = "my-project"
version = "0.1.0"
requires-python = ">=3.11"
dependencies = [
    "fastapi>=0.110.0,<1.0.0",
    "pydantic>=2.7.0,<3.0.0",
    "pydantic-settings>=2.2.0",
    "sqlalchemy>=2.0.28",
    "alembic>=1.13.1",
]

[project.optional-dependencies]
dev = [
    "pytest>=8.0.0",
    "pytest-asyncio>=0.23.0",
    "ruff>=0.3.0",
    "httpx>=0.27.0",
]
# Add a single new dependency cleanly with uv
uv add "scikit-learn>=1.4.0"
# Or for development
uv add --dev "pytest-cov>=5.0.0"

JavaScript / Node Dependency Protocol (package.json)

# Add runtime dependency
npm install @tanstack/react-query@^5.0.0

# Add dev dependency
npm install --save-dev @types/node@^20.0.0

4. What Decisions Should I Make?

SituationDecision Rule
Adding a lightweight helper functionPrefer writing a small local utility in utils/ instead of pulling an entire heavy external package.
Version Pinning StrategyUse compatible release operator (~= or >=X.Y.Z,<(X+1).0.0) for libraries; exact pin (==X.Y.Z) for critical ML framework combinations (e.g. tensorflow==2.16.1 + keras==3.3.3).
Resolving ConflictsIdentify the exact conflicting constraint using uv pip tree or pip check. Never indiscriminately update 10 packages at once.
Dev vs RuntimeTest runners, linters, formatters, type stubs (@types/*, mypy, ruff, pytest) must strictly reside in dev-dependencies.

5. What Should I Avoid?

  • NEVER solve conflicts by random version bumping: Pinpointing the root conflict is mandatory.
  • NEVER add unpinned unbounded dependencies: Avoid bare package names with no constraints (requests vs requests>=2.31.0,<3.0.0).
  • NEVER edit uv.lock or package-lock.json manually: Always let the package manager generate the lockfile.
  • NEVER use multiple package managers in the same project: Avoid mixing pip, poetry, and conda concurrently in a single repo.

6. How Should I Verify Success?

# 1. Python dependency check
python -m pip check

# 2. Test import of newly added package
python -c "import <new_package>; print('<new_package> imported successfully')"

# 3. Node dependency audit
npm audit --audit-level=high

# 4. Run test suite to verify no transitive breakages
pytest -v

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.