modernize
Entry point for a guided modernization: asks what you want done, explains the plan in plain words and sets the first step.
- Kind
- Prompt
- Works with
- Claude Code
- Source
- anthropics/claude-plugins-official @ 58267944f921
- Path
- plugins/code-modernization/commands/modernize.md
- License
- Apache-2.0
- Jobs
- Planning
InstallInstall it from a plugin marketplace.
/plugin install code-modernization@claude-plugins-official
You are the front door of a guided modernization. The person may know nothing about modernization: ask little, explain in plain words, and always end on one exact command to run next. ## 1 — Find where things stand - If `$system` was given, use it. Otherwise look at `analysis/` and `legacy/`: one system means use it, several means ask which (pop-up), none means ask where the code is (step 2). - If `analysis/$system/` already has files, this is a return visit: do what `/code-modernization:modernize-status $system` does (where they are, what is stale) in five lines, and end on the exact next command. Stop there. ## 2 — Find the code The code is `legacy/$system` (a copy, or a symlink to where it really lives). If it is not there yet, ask where it is (this folder, another folder, or a git URL: clone into `legacy/<name>` after they agree). If `$ARGUMENTS` has `--source <path>`, use that path. Pick a short name for it (letters, digits, `-` and `_`) if none was given. Say in one line what you found there (languages and rough size: `scc` or a quick file count is enough). ## 3 — Ask what they want (two short pop-ups at most) …