Execute code modernization projects with a structured lifecycle.
Install
mkdir -p .claude/skills/modernize && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/16293" && unzip -o skill.zip -d .claude/skills/modernize && rm skill.zipInstalls to .claude/skills/modernize
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.
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.Key capabilities
- →Assess modernization efforts in repositories
- →Plan code migrations following a defined lifecycle
- →Execute multi-phase modernization projects
- →Enforce quality gates during modernization
- →Conduct retrospective process improvements
- →Use repo scripts for dependency analysis and testing
How it works
This skill orchestrates modernization efforts by following a lifecycle (assess -> plan -> execute -> retro) and enforcing quality gates. It uses repo scripts and adheres to `AGENTS.md` for configuration.
Inputs & outputs
When to use modernize
- →Assess modernization effort
- →Plan code migration
- →Execute multi-phase refactoring
About this skill
Modernize
Use this skill when the user wants Codex to assess, plan, execute, or retrospect on a modernization effort.
Start Here
- Read
AGENTS.mdfirst for testing, logging, and documentation rules. - Use the lifecycle in references/lifecycle.md.
- Use references/source-map.md for the canonical protocol and script sources.
- Preserve the repo's quality gates; do not weaken them during migration.
Operating Rules
- Follow the lifecycle: assess -> plan -> execute -> retro -> apply improvements.
- Keep specialist separation: coordinator, security, architect, coder, tester, documentation.
- Use repo scripts for dependency analysis, stage testing, validation, and history logging.
- Treat
AGENTS.mdas the primary configuration source; useCLAUDE.mdonly as legacy fallback. - If Compound Engineering
ce-*skills are available in your environment, prefer them oversuperpowers:*and bare-name toolkit skills per the precedence table in the command protocol's Optional skill enhancements section.
When To Read More
- For workflow sequencing: references/lifecycle.md
- For source mapping and quality gates: references/source-map.md
When not to use it
- →When the repository does not follow the modernize workflow
- →When the user does not want to assess, plan, execute, or retrospect on modernization
- →When the task involves weakening quality gates
Limitations
- →Requires repositories to follow the modernize workflow
- →Does not permit weakening quality gates during migration
- →Treats `AGENTS.md` as the primary configuration source
How it compares
This skill provides a structured, lifecycle-driven approach to modernization with explicit quality gate enforcement and specialist separation, ensuring a controlled and rigorous process.
Compared to similar skills
modernize side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| modernize (this skill) | 0 | 3mo | No flags | Advanced |
| mlops-industrialization | 1 | 6mo | No flags | Intermediate |
| plain-upgrade | 1 | 2mo | No flags | Intermediate |
| dotnet-upgrade | 0 | 4mo | No flags | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
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.
plain-upgrade
dropseed
Upgrades Plain packages and applies required migration changes. Use when updating to newer package versions.
dotnet-upgrade
ComeOnOliver
Ready-to-use prompts for comprehensive .NET framework upgrade analysis and execution
simplification-cascades
mrgoonie
Find one insight that eliminates multiple components - "if this is true, we don't need X, Y, or Z"
deployment-procedures
davila7
Production deployment principles and decision-making. Safe deployment workflows, rollback strategies, and verification. Teaches thinking, not scripts.
schedules
windmill-labs
MUST use when configuring schedules.