code-modernization

Plugin code-modernization from marketplace claude-plugins-official in jrezelorezo/gh-repo-clone-anthropics-claude-plugins-official. Commands read from the repo's manifest — 19 days ago.

Slash commands (10)

• /code-modernization:modernize-assess

  Full discovery & portfolio analysis of a legacy system — inventory, complexity, debt, relative scale

• /code-modernization:modernize-brief

  Generate a phased Modernization Brief — the approved plan that transformation agents will execute against

• /code-modernization:modernize-extract-rules

  Mine business logic from legacy code into testable, human-readable rule specifications

• /code-modernization:modernize-harden

  Security vulnerability scan with a reviewable remediation patch — OWASP, CWE, CVE, secrets, injection

• /code-modernization:modernize-map

  Dependency & topology mapping — call graphs, data lineage, batch flows, rendered as navigable diagrams

• /code-modernization:modernize-preflight

  Environment readiness check — analysis tools, build toolchain, source completeness, telemetry access

• /code-modernization:modernize-reimagine

  Multi-agent greenfield rebuild — extract specs from legacy, design AI-native, scaffold & validate with HITL

• /code-modernization:modernize-status

  Where am I in the modernization workflow — artifact inventory, staleness, secrets hygiene, next step

• /code-modernization:modernize-transform

  Transform one legacy module to the target stack — idiomatic rewrite with behavior-equivalence tests

• /code-modernization:modernize-uplift

  Same-stack version uplift (e.g. .NET Framework 4.8 → .NET 8) — preserve the code, fix the version deltas, prove equivalence by running one test suite on both runtimes

Subagents (7)

• architecture-critic

  Reviews proposed target architectures and transformed code against modern best practice. Adversarial — looks for over-engineering, missed requirements, and simpler alternatives.

• business-rules-extractor

  Mines domain logic, calculations, validations, and policies from legacy code into testable Given/When/Then specifications. Use when you need to separate "what the business requires" from "how the old code happened to implement it.

• legacy-analyst

  Deep-reads legacy codebases (COBOL, Java, .NET, Node, anything) to build structural and behavioral understanding. Use for discovery, dependency mapping, dead-code detection, and "what does this system actually do" questions.

• scaffolder

  Scaffolds one service of a reimagined system from the approved architecture and spec — project skeleton, domain model, API stubs, executable acceptance tests. Write access is scoped to its own service directory under modernized/.

• security-auditor

  Adversarial security reviewer — OWASP Top 10, CWE, dependency CVEs, secrets, injection. Use for security debt scanning and pre-modernization hardening.

• test-engineer

  Writes characterization, contract, and equivalence tests that pin down legacy behavior so transformation can be proven correct. Use before any rewrite.

• version-delta-analyst

  Identifies the breaking changes between two versions of the SAME stack (e.g. .NET Framework 4.8 → .NET 8, Java 8 → 17/21, Spring Boot 2 → 3) that actually bite a given codebase, and drives the ecosystem's migration tooling. Use for same-stack uplifts, where code is preserved and tweaked — not rewrit

Similar plugins