agentleFS
letsrevelletsrevel/revel-backend/.claude/skills/updating-deps/SKILL.md

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).

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
  1. Distinctive:

    Check release notes/changelog before updating

    line 55
  2. Very specific:

    Django: Keep at latest 5.2.x LTS (>=5.2.x,<6.0)

    line 58
  3. Very specific:

    Check classifier in pyproject.toml: "Framework :: Django :: 5.2"

    line 59
  4. Distinctive:

    Run all checks to ensure nothing broke:

    line 71
  5. Very specific:

    Search for usage: grep -r "import <pkg>" src/

    line 82
  6. Very specific:

    Check reverse deps: uv pip show <pkg> | grep Required-by

    line 83

≈ “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.

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

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.toml under [project] dependencies and [dependency-groups] dev
  • Django is pinned to 5.2.x LTS (>=5.2.x,<6.0)

Step 1: Check Outdated Dependencies

uv pip list --outdated

This 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/aiogram
  • pygments - 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 --dev

Step 5: Verify

Run all checks to ensure nothing broke:

make check

This runs: format, lint, mypy, i18n-check

Common Patterns

Remove Unused Dependency

  1. Search for usage: grep -r "import <pkg>" src/
  2. Check reverse deps: uv pip show <pkg> | grep Required-by
  3. Remove from pyproject.toml
  4. Run uv sync --dev

Move to Dev Dependencies

  1. Remove from [project] dependencies
  2. Add to [dependency-groups] dev
  3. 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 - unused
  • freezegun in prod - duplicate (already in dev)
  • multidict - transitive from aiohttp
  • ninja-schema - unused
  • pyopenssl - unused
  • pygments - transitive from dev deps
  • types-tqdm - moved to dev
  • piexif - moved to dev (only used in tests)

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.