Menu
Upgrade Python dependencies using uv, then run post-upgrade checks to ensure nothing is broken.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Interactively fix any type checking issues in Python code
Use when the user asks to create, view, or modify a SaaS Pegasus project via the `pegasus` CLI — e.g. "create a new Pegasus project for X", "add subscriptions to my Pegasus project", "show me my project settings", "switch the front-end framework to React", "what features can I use on my license tier".
Resolve merge conflicts when upgrading SaaS Pegasus. Use when the user has merge conflicts after running git merge during a Pegasus upgrade, or when they need help with the merge process. Also use when the user mentions 'merge pegasus".
Upgrade JavaScript dependencies using npm-check-updates, then run post-upgrade checks to ensure nothing is broken.
Upgrade to the latest version of SaaS Pegasus. Use when the user mentions 'upgrade pegasus,' or 'pegasus upgrade.'
| name | upgrade-python-deps |
| description | Upgrade Python dependencies using uv, then run post-upgrade checks to ensure nothing is broken. |
| allowed-tools | ["Bash(uv lock *)","Bash(uv sync *)","Bash(make test *)","Bash(uv run mypy *)"] |
Upgrade all Python dependencies and verify nothing is broken.
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.
Run uv sync to install the upgraded dependencies into the virtual environment.
Run these checks sequentially, stopping if any step fails:
uv run mypy . and report any new type errors. These may be caused
by updated type stubs or changes in library APIs.make test to verify the test suite still passes.Summarize what was done:
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.