How do I install the Upgrade Pegasus skill?

Run npx skillmds@latest add saaspegasus/upgrade-pegasus in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Upgrade Pegasus safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Upgrade Pegasus?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Upgrade Pegasus free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Upgrade Pegasus?

saaspegasus (@saaspegasus) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Upgrade Pegasus by saaspegasus — Agent Skill

Name: Upgrade Pegasus
Author: saaspegasus

File contents

Upgrading Pegasus

Instructions

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.

Before pushing

Ensure main is up to date: Run git checkout main && git pull before starting the upgrade. The merge will be against main, so it must have the latest changes.

Pushing

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

Custom PR title

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.

After the push completes

Run git fetch origin to see the new branch
The branch name will be in the format pegasus-<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)
Merge the user's default branch (usually main) into the upgrade branch using your "resolve pegasus conflicts" skill. That skill owns the post-merge verification and push flow.

---name: upgrade-pegasusdescription: Upgrade to the latest version of SaaS Pegasus. Use when the user mentions 'upgrade pegasus,' or 'pegasus upgrade.'---# Upgrading Pegasus## InstructionsThis 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.### Before pushing1. **Ensure main is up to date**: Run `git checkout main && git pull` before starting the upgrade. The merge will be against main, so it must have the latest changes.### PushingUse 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).#### Custom PR titleIf 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.### After the push completes1. Run `git fetch origin` to see the new branch2. The branch name will be in the format `pegasus-<version>-<timestamp>` (e.g. `pegasus-2026.2.1.3-1771252378.779356`)3. `git checkout <branch-name>` to switch to it (it will already be up to date from the push)4. Merge the user's default branch (usually `main`) into the upgrade branch using your "resolve pegasus conflicts" skill. That skill owns the post-merge verification and push flow.

Frequently asked questions

Upgrade Pegasus