mcpField
U
upgrade-python-deps

upgrade-python-deps

github.com/saaspegasusDevelopment32182 installsUpdated 12w ago
Repository

About upgrade-python-deps

upgrade-python-deps is a skill for upgrading Python dependencies with uv and checking the project afterward. It runs type checks and tests, then summarizes changes and asks before committing.

Key features

  1. 01Upgrade compatible dependencies in the lock file
  2. 02Apply a seven-day release cooldown
  3. 03Sync the virtual environment
  4. 04Run mypy and project tests
  5. 05Summarize results and request commit approval

Use cases

  1. 01Refreshing a project's Python dependency lock file
  2. 02Checking type errors after library updates
  3. 03Verifying tests before considering a dependency commit

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/saaspegasus/django-skills --skill upgrade-python-deps

After installing, type/upgrade-python-depsin Claude Code to confirm it loaded.

Details

From the project README

Your task

Upgrade all Python dependencies and verify nothing is broken.

Step 1: Upgrade the lock file

Run uv lock --upgrade --exclude-newer "7 days" to upgrade all dependencies to their latest compatible versions (with a 7-day cooldown to mitigate supply-chain attacks).

Review the output for any resolution errors. If there are conflicts, report them to the user and ask how to proceed before continuing.

Step 2: Sync the environment

Run uv sync to install the upgraded dependencies into the virtual environment.

Step 3: Run post-upgrade checks

Run these checks sequentially, stopping if any step fails:

  • Type checking: Run uv run mypy . and report any new type errors. These may be caused by updated type stubs or changes in library APIs.
  • Tests: Run make test to verify the test suite still passes.
Step 4: Summarize and commit

Summarize what was done:

  • Which packages were upgraded (notable version changes)
  • Whether any type errors were introduced
  • Whether all tests passed
  • Any issues that need manual attention

If there were failures, present the issues and ask how the user wants to proceed.

If everything passed, ask the user if they'd like to commit the changes. If yes, commit using the /commit skill.

Comments

Markdown supported