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
- kinhluan/skillstheir own version, first seen Nov 8, 2026
- REPOZY/superpowers-optimizedtheir own version, first seen Nov 8, 2026
- AnyOrgName/php-skillstheir own version, first seen Nov 8, 2026
- SWEStash/swe-workflow-skillstheir own version, first seen Nov 8, 2026
- KMaruthi2002/universal-llm-skillstheir own version, first seen Oct 25, 2026
- Mushfiqur-Rahman-Robin/coding-rulestheir own version, first seen Oct 13, 2026
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.
mmondoraSkillinfrastructure-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 AzureSkillrelease-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 AzureSkillgit-workflow
Squad branching model: dev-first workflow with insiders preview channel
Also in 7 projects that use this
pproencaSkillrefactoring
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
shanggqmSkilldata-analysis
数据分析技能,提供结构化的数据查询、统计分析和报告生成工作流。当用户需要查询数据库、进行数据统计分析、生成分析报告时使用。按规范输出原始数据、计算结果、Markdown报告和HTML可视化报告。
Also in 3 projects that use this
0xSeroSkillsecurity
Also in 3 projects that use this
Other versions18 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 18
- derHaken/SuperAntigravity★ 439same name
- REPOZY/superpowers-optimized★ 146same name
- robisson/build-like-amazon-agent-skills★ 16same name
- kinhluan/skills★ 6same name
- AnyOrgName/php-skills★ 4same name
- dprakash2101/dotnet-production-agent-skills★ 4same name
- saitarrun/Devforge-ai★ 4same name
- bchox/agent-practices★ 2same name
- JhonatanMota/claude-skills★ 1same name
- KMaruthi2002/universal-llm-skills★ 1same name
8 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository30 other files it gives its agents.
- AGENTS.mdAGENTS.md
- adr-managementSkill
- agentic-developmentSkill
- ci-cdSkill
- code-architectureSkill
- database-postgresqlSkill
- data-engineeringSkill
- debuggingSkill
- deep-learningSkill
- deploymentSkill
- dockerSkill
- documentation-orchestratorSkill
- documentationSkill
- environment-guardrailsSkill
- frontend-react-typescriptSkill
- git-githubSkill
- machine-learningSkill
- observabilitySkill
- performance-optimizationSkill
- portfolio-readinessSkill
- project-bootstrapSkill
- project-knowledgeSkill
- python-apiSkill
- python-environmentSkill
- rag-ocr-llmSkill
- release-engineeringSkill
- reusable-componentsSkill
- security-secretsSkill
- supply-chain-securitySkill
- testing-qualitySkill
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
- Distinctive: line 10
Use this skill when:
- Very specific: line 16
Do NOT use this skill for initial environment bootstrapping (use python-environment).
- Very specific: line 26
Check if the desired library is already pulled in as a sub-dependency (uv pip tree or npm ls <pkg>).
- Very specific: line 27
Runtime Compatibility: Check current Python version (e.g.
- Very specific: line 107
NEVER add unpinned unbounded dependencies: Avoid bare package names with no constraints (requests vs requests>=2.31.0,<3.0.0).
- Very specific: line 108
NEVER edit
uv.lockorpackage-lock.jsonmanually: Always let the package manager generate the lockfile. - Very specific: line 109
NEVER use multiple package managers in the same project: Avoid mixing pip, poetry, and conda concurrently in a single repo.
“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.
Files
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?
- Manifest Files:
- Python:
pyproject.toml,requirements.txt,requirements-dev.txt,uv.lock,poetry.lock. - Node:
package.json,package-lock.json.
- Python:
- Current Constraints & Transitive Trees:
- Check if the desired library is already pulled in as a sub-dependency (
uv pip treeornpm ls <pkg>).
- Check if the desired library is already pulled in as a sub-dependency (
- 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 ChangesPython 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.04. What Decisions Should I Make?
| Situation | Decision Rule |
| Adding a lightweight helper function | Prefer writing a small local utility in utils/ instead of pulling an entire heavy external package. |
| Version Pinning Strategy | Use 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 Conflicts | Identify the exact conflicting constraint using uv pip tree or pip check. Never indiscriminately update 10 packages at once. |
| Dev vs Runtime | Test 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 (
requestsvsrequests>=2.31.0,<3.0.0). - NEVER edit
uv.lockorpackage-lock.jsonmanually: Always let the package manager generate the lockfile. - NEVER use multiple package managers in the same project: Avoid mixing
pip,poetry, andcondaconcurrently 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 -vDoes 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
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.

