plain-upgrade
This utility manages version upgrades, changelog generation, and environment validation for Plain packages.
Install
mkdir -p .claude/skills/plain-upgrade && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/5617" && unzip -o skill.zip -d .claude/skills/plain-upgrade && rm skill.zipInstalls to .claude/skills/plain-upgrade
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Upgrades Plain packages and applies required migration changes. Use when updating to newer package versions.Key capabilities
- →Upgrade package versions
- →Summarize changelog differences
- →Sync agent rules
- →Run automated validation checks
How it works
Executes package management commands to update versions, extracts changelog data, and triggers validation scripts.
Inputs & outputs
When to use plain-upgrade
- →Update Plain package versions
- →Review changelogs for breaking changes
- →Run automated post-upgrade validation
About this skill
Upgrade Plain Packages
1. Run the upgrade
uv run plain upgrade [package-names...]
This will show which packages were upgraded (e.g., plain-postgres: 0.1.0 -> 0.2.0).
2. Review the changelog for each upgraded package
For each package that was upgraded:
- Run
uv run plain changelog <package> --from <old-version> --to <new-version> - Read both sections:
- "What's changed" — new features, behavior changes, bug fixes worth knowing about
- "Upgrade instructions" — required code changes (or "No changes required")
- If there are required code changes, apply them
- Capture a short summary of "What's changed" for the final report — surface new APIs, new settings, new CLI commands, performance improvements, and notable bug fixes even when no code changes are required. Skip pure internal cleanup.
3. Update agent rules and skills
Run uv run plain agent install to sync any updated rules and skills from the upgraded packages.
4. Validate
- Run
uv run plain fixto fix formatting - Run
uv run plain checkto validate (linting, preflight, migrations, tests)
5. Report
For each upgraded package, report:
- Version bump (e.g.,
plain-postgres: 0.103.0 -> 0.105.0) - A 1-3 bullet summary of notable changes from "What's changed" (new features, behavior changes, perf wins, notable fixes)
- What code changes were applied (or "no code changes required")
Guidelines
- Process ALL packages before testing
- DO NOT commit any changes
- Keep code changes minimal and focused
- Report any issues or conflicts encountered
When not to use it
- →Upgrading non-Plain packages
- →When manual migrations are already completed
Prerequisites
Limitations
- →Cannot automate all breaking logic changes
- →Requires post-upgrade manual review
How it compares
It automates the entire migration loop (check, update, validate) instead of just bumping version strings.
Compared to similar skills
plain-upgrade side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| plain-upgrade (this skill) | 1 | 2mo | No flags | Intermediate |
| mlops-industrialization | 1 | 6mo | No flags | Intermediate |
| dotnet-upgrade | 0 | 4mo | No flags | Intermediate |
| modernize | 0 | 3mo | No flags | Advanced |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by dropseed
View all by dropseed →You might also like
mlops-industrialization
fmind
Guide to transform prototypes into robust, distributable Python packages using the src layout, hybrid paradigm, and strict configuration management.
dotnet-upgrade
ComeOnOliver
Ready-to-use prompts for comprehensive .NET framework upgrade analysis and execution
modernize
laird
Use this skill for modernization assessments, migration planning, multi-phase modernization execution, quality-gate enforcement, and retrospective process improvement in repositories that follow the modernize workflow.
software-architecture
davila7
Guide for quality focused software architecture. This skill should be used when users want to write code, design architecture, analyze code, in any case that relates to software development.
effective-go
openshift
Apply Go best practices, idioms, and conventions from golang.org/doc/effective_go. Use when writing, reviewing, or refactoring Go code to ensure idiomatic, clean, and efficient implementations.
solid-principles
SmidigStorm
Enforce SOLID principles (Single Responsibility, Open/Closed, Liskov Substitution, Interface Segregation, Dependency Inversion) in object-oriented design. Use when writing or reviewing classes and modules.