Menu
Upgrade to the latest version of SaaS Pegasus. Use when the user mentions 'upgrade pegasus,' or 'pegasus upgrade.'
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 Python dependencies using uv, then run post-upgrade checks to ensure nothing is broken.
| name | upgrade-pegasus |
| description | Upgrade to the latest version of SaaS Pegasus. Use when the user mentions 'upgrade pegasus,' or 'pegasus upgrade.' |
This skill helps users upgrade their SaaS Pegasus codebase.
Use the pegasus-cli to trigger the upgrade. It can be called via the pegasus command in the project's python environment.
You first need to list the user's project and find the right one.
pegasus projects list
You should be able to compare the project names to what's defined pegasus-config.yaml to find the right id.
Before running any pegasus commands, confirm auth with pegasus auth status (non-interactive). If it reports unauthenticated, ask the user to run pegasus auth login in a separate terminal — it's interactive and will hang if invoked from this session. See the pegasus-projects skill's Setup section for the full flow.
git checkout main && git pull before starting the upgrade. The merge will be against main, so it must have the latest changes.Use the CLI flags to avoid interactive prompts:
# Upgrade to latest stable version (non-interactive):
pegasus projects push <project_id> --upgrade
# Upgrade to latest dev version (non-interactive):
pegasus projects push <project_id> --dev
Important: Always pass --upgrade or --dev to avoid interactive prompts that require stdin.
Without these flags, the CLI will show an interactive menu that doesn't work well in non-interactive environments.
If the user doesn't specify stable vs dev, default to --upgrade (stable).
If the user asks for a specific pull request title (e.g. "use PR title X" or "call the PR Y"), pass it via --pr-title:
pegasus projects push <project_id> --upgrade --pr-title "Your custom title"
If the user doesn't mention a title, omit the flag — the server generates a sensible default based on the version.
git fetch origin to see the new branchpegasus-<version>-<timestamp> (e.g. pegasus-2026.2.1.3-1771252378.779356)git checkout <branch-name> to switch to it (it will already be up to date from the push)main) into the upgrade branch using your "resolve pegasus conflicts" skill. That skill owns the post-merge verification and push flow.