updating-deps
Skill119 starsChanged 3 months agoMITView on GitHub
Update Python dependencies using UV. Scan for outdated packages, identify unused dependencies, and safely update pyproject.toml while respecting version constraints (e.g., Django LTS).
In this repository5 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- loki-logsSkill
- silk-debugSkill
- update-changelogSkill
- whats-newSkill
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 2 are distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 55
Check release notes/changelog before updating
- Very specific: line 58
Django: Keep at latest 5.2.x LTS (>=5.2.x,<6.0)
- Very specific: line 59
Check classifier in pyproject.toml: "Framework :: Django :: 5.2"
- Distinctive: line 71
Run all checks to ensure nothing broke:
- Very specific: line 82
Search for usage: grep -r "import <pkg>" src/
- Very specific: line 83
Check reverse deps: uv pip show <pkg> | grep Required-by
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Dependency Update Workflow
A structured approach for updating Python dependencies in this UV-managed project.
Prerequisites
- This project uses UV for dependency management (never pip directly)
- Dependencies are in
pyproject.tomlunder[project] dependenciesand[dependency-groups] dev - Django is pinned to 5.2.x LTS (
>=5.2.x,<6.0)
Step 1: Check Outdated Dependencies
uv pip list --outdatedThis shows all outdated packages. Focus on top-level dependencies listed in pyproject.toml.
Step 2: Identify Unused Dependencies
For each suspicious dependency, search for actual usage:
# Check for imports
grep -r "from <package>|import <package>" src/
# Check if it's a transitive dependency
uv pip show <package> | grep -i "required-by"Known Transitive Dependencies (safe to remove from explicit deps)
These are pulled in automatically by other packages:
multidict- transitive from aiohttp/aiogrampygments- transitive from mkdocs-material, pytest
Type Stubs Belong in Dev
Move types-* packages to [dependency-groups] dev, not production dependencies.
Step 3: Categorize Updates
Safe Updates (patch/minor, no breaking changes)
- Patch versions:
1.2.3→1.2.4 - Minor versions with good release notes:
1.2.x→1.3.x
Needs Review (major versions)
- Major bumps:
1.x→2.x - Check release notes/changelog before updating
Version-Pinned Dependencies
- Django: Keep at latest 5.2.x LTS (
>=5.2.x,<6.0) - Check classifier in pyproject.toml:
"Framework :: Django :: 5.2"
Step 4: Apply Updates
Edit pyproject.toml directly, then sync:
uv sync --devStep 5: Verify
Run all checks to ensure nothing broke:
make checkThis runs: format, lint, mypy, i18n-check
Common Patterns
Remove Unused Dependency
- Search for usage:
grep -r "import <pkg>" src/ - Check reverse deps:
uv pip show <pkg> | grep Required-by - Remove from pyproject.toml
- Run
uv sync --dev
Move to Dev Dependencies
- Remove from
[project] dependencies - Add to
[dependency-groups] dev - Run
uv sync --dev
Pin to Major Version
# Allow patches within LTS
"django>=5.2.11,<6.0"Dependencies Removed (2026-02-04)
For reference, these were removed as unused/transitive:
django-extension- typo (django-extensions already present)django-money- unusedfreezegunin prod - duplicate (already in dev)multidict- transitive from aiohttpninja-schema- unusedpyopenssl- unusedpygments- transitive from dev depstypes-tqdm- moved to devpiexif- moved to dev (only used in tests)
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
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.

