plain-upgrade

Automate Plain package upgrades and apply required migrations with uv run.

1.0k|27|Updated Mar 22, 2023
One-click install
npx skills add https://github.com/dropseed/plain --skill plain-upgrade
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plain-upgrade
Source: https://github.com/dropseed/plain/tree/main/plain/plain/agents/.claude/skills/plain-upgrade
Command: npx skills add https://github.com/dropseed/plain --skill plain-upgrade

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Upgrading Plain packages and applying required migration changes is error-prone and time-consuming when managing multiple packages across a project. This Skill automates the upgrade workflow, ensuring that changes are consistently applied and that the project remains in a valid state.

Core Features & Use Cases

  • Automates multi-package upgrades and tracks version changes.
  • Applies per-package migration instructions and ensures compatibility.
  • Keeps agent rules and project tooling in sync after upgrades.

Quick Start

Run uv run plain upgrade [package-names...] to upgrade specified packages and trigger the migration workflow.

Frequently Asked Questions about plain-upgrade

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate package upgrades and migrations for a Plain project?

You can automate Plain package upgrades by running uv run plain upgrade, which applies version changes, reads migration instructions, and validates the project state using plain fix and plain check.

What is the best way to manage multiple package upgrades in Plain without breaking migrations?

Managing multiple Plain package upgrades safely requires an automated workflow that tracks version changes, applies per-package migration instructions, and synchronizes agent rules to ensure compatibility across the project.

Do I need uv to run Plain package migrations and apply code modifications?

Yes, you need uv to run Plain package migrations, as the upgrade workflow requires the uv run command to read upgrade instructions, apply code modifications, and execute validation checks.

Can I synchronize agent rules and project tooling after upgrading Plain packages?

Yes, upgrading Plain packages automatically synchronizes agent rules and project tooling as part of the migration workflow, ensuring your automation and validation rules remain compatible with the new package versions.

Why does my Plain project fail validation after a manual package upgrade?

Manual Plain package upgrades often fail validation because required migration changes and agent-rule synchronization are skipped, whereas the automated upgrade workflow applies these modifications and runs plain fix and plain check to maintain a valid state.