Upgrade reinhardt-web version with guided migration analysis, breaking change detection, and code modification assistance
How this command is triggered — by the user, by Claude, or both
Slash command
/reinhardt-agents-plugin:reinhardt-upgradeThe summary Claude sees in its command listing — used to decide when to auto-load this command
# Reinhardt Version Upgrade
You are guiding the user through upgrading their reinhardt-web dependency. Follow this workflow:
## Step 1: Detect Current Version
Read the project's `Cargo.toml` and extract the current reinhardt version:
- Look for `reinhardt = { version = "..." }` in `[dependencies]`
- Report the detected version to the user
If no reinhardt dependency is found, inform the user this command is for reinhardt-web projects only.
## Step 2: Ask Target Version
Ask the user which version they want to upgrade to:
- Accept specific versions (e.g., `0.1.3`, `0.2.0`)
- Accept `la...You are guiding the user through upgrading their reinhardt-web dependency. Follow this workflow:
Read the project's Cargo.toml and extract the current reinhardt version:
reinhardt = { version = "..." } in [dependencies]If no reinhardt dependency is found, inform the user this command is for reinhardt-web projects only.
Ask the user which version they want to upgrade to:
0.1.3, 0.2.0)latest — resolve via gh release list -R kent8192/reinhardt-web --limit 1 or by reading reinhardt/Cargo.toml if the repo is available locallyPresent the upgrade plan:
Upgrading reinhardt: {current} → {target}
This will:
- Analyze CHANGELOG and GitHub PRs for breaking changes
- Scan your code for deprecated API usage
- Guide you through necessary code modifications
- Update Cargo.toml and verify with cargo check
Proceed?
After confirmation, invoke the migration skill which handles:
Before starting, verify:
git status --porcelain returns empty)npx claudepluginhub kent8192/reinhardt-agents-plugin --plugin reinhardt-agents-plugin