Back to catalog
Human reviewedDevelopment

Skill dossier

legacy-modernizer

Source declaration

Designs incremental migration strategies, identifies service boundaries, produces dependency maps and migration roadmaps, and generates API facade designs for aging codebases. Use when modernizing legacy systems, implementing strangler fig pattern or branch by abstraction, decomposing monoliths, upgrading frameworks or languages, or reducing technical debt without disrupting business operations.

The author's original description, preserved in English. It describes intent, not verified performance.

Designs incremental migration strategies, identifies service boundaries, produces dependency maps and migration roadmaps, and generates API facade designs for aging codebases. Use when modernizing legacy systems, implementing strangler fig pattern or branch by abstraction, decomposing monoliths, upgrading frameworks or languages, or reducing technical debt without disrupting business operations.

developmentreferences

Research summary

Human reviewed

Skill Atlas editorial review · editorial-preview-1.0.0

An architecture Skill for incremental legacy migration: assess, plan with rollback, build characterization tests, then strangler-fig the system behind a facade.

Review scope

Deterministic static analysis of collected SKILL.md and supporting text/code. Machine-assisted candidates and findings await human editorial review; no dynamic behavior or effect is assessed.

Observable capabilities

  • Produces a dependency map and risk register for the existing system.
  • Plans phased migrations with rollback triggers and owners.
  • Builds characterization tests targeting 80 percent coverage before changes.
  • Routes traffic through a facade with feature flags in staged increments.

Limitations & scope

  • Code examples are Python; other stacks must be adapted.
  • Traffic shifting and monitoring need infrastructure the skill does not provide.
  • The example percentages and thresholds are illustrative and not validated here.

Relevant for

  • Teams decomposing monoliths
  • Engineers upgrading aging frameworks
  • Tech leads planning risk-controlled migrations

What ships with the skill

The file inventory comes from the collected source at the recorded commit. Paths and sizes are structural observations, not a measure of quality.

files
6
Markdown files
6
scripts
0
references
5
Size
63.8 KB
Structural complexity
Low

File inventory

PathTypeBytes
skills/legacy-modernizer/references/legacy-testing.mdReference11.2 KB
skills/legacy-modernizer/references/migration-strategies.mdReference11.5 KB
skills/legacy-modernizer/references/refactoring-patterns.mdReference11.9 KB
skills/legacy-modernizer/references/strangler-fig-pattern.mdReference8.2 KB
skills/legacy-modernizer/references/system-assessment.mdReference14.8 KB
skills/legacy-modernizer/SKILL.mdInstruction6.1 KB

SKILL.md frontmatter

{
  "name": "legacy-modernizer",
  "description": "Designs incremental migration strategies, identifies service boundaries, produces dependency maps and migration roadmaps, and generates API facade designs for aging codebases. Use when modernizing legacy systems, implementing strangler fig pattern or branch by abstraction, decomposing monoliths, upgrading frameworks or languages, or reducing technical debt without disrupting business operations.",
  "license": "MIT",
  "metadata": {
    "author": "https://github.com/Jeffallan",
    "company": "https://synergetic.solutions",
    "version": "1.1.0",
    "domain": "specialized",
    "triggers": "legacy modernization, strangler fig, incremental migration, technical debt, legacy refactoring, system migration, legacy system, modernize codebase",
    "role": "specialist",
    "scope": "architecture",
    "output-format": "analysis-and-code",
    "related-skills": "test-master, devops-engineer"
  }
}

A reading of the operating sequence

This workflow reconstructs the apparent sequence from source material. Unless controlled evaluation is explicitly recorded, it is provisional—not an observed trace.

  1. 01
    Input

    Assess the system

    Analyze codebase, dependencies, risks and constraints; produce a dependency map and risk register.

  2. 02
    Action

    Migrate incrementally

    Apply the strangler fig pattern with feature flags, routing traffic via a facade.

  3. 03
    Decision

    Check metrics per increment

    Verify error rates and latency stay within baseline after each traffic increase.

  4. 04
    Output

    Deliver plan and code

    Provide assessment summary, migration plan, implementation code, tests and monitoring setup.

Potential risk surfaces

Static findings identify points to inspect before installation. They do not establish that a skill is safe, malicious, or effective.

Attention recommended

90 deterministic lexical finding(s) require review across the collected text. Findings can occur in documentation and do not prove execution or exploitability; binary-only files were not scanned.

Network accessObserved
File writesObserved
Credential useObserved
Note

File modification is described or implemented

82 occurrences

This line contains a possible file-write or redirection operation. Check destination paths and overwrite behavior; the static review did not write any file. This rule matched 82 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

Medium

Network access is mentioned

7 occurrences

A URL or network client appears in this source line. Review destinations, data sent, and trust boundaries; static text cannot establish actual network activity. This rule matched 7 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

High

Credential or secret material is referenced

This line resembles a credential literal or reads a sensitive environment value. Do not expose its contents; verify whether it is a placeholder, required secret, or accidentally committed material. This rule matched 1 location(s) in the collected text; 1 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

Editorial security note

Review feature-flag and traffic-routing changes carefully, since they alter production behavior.

Where context can be spent

Discovery, activation, and resource layers have different meanings. Exact values appear only when the official token-counting method was run with a named model.

Exact token counts unavailable

All token values, including per-file inventory, are null until the pipeline performs an official exact count with an explicit model.

No token measurement was recorded with the required official method. This dossier does not substitute character counts, file sizes, or estimates.

Controlled evaluation

No controlled evaluation

This skill has only the evidence identified above. No task success, token efficiency, latency, or quality advantage is claimed.

Not tested

Use with the source in view

Install command
git clone https://github.com/Jeffallan/claude-skills.git cd claude-skills # Copy this skill directory into one of: # ~/.claude/skills/legacy-modernizer # .claude/skills/legacy-modernizer
  1. Open the pinned source at https://github.com/Jeffallan/claude-skills/blob/67c1961b180dc92cf08983344627109e983e8f51/skills/legacy-modernizer/SKILL.md.
  2. Review the license, prerequisites and all bundled reference files.
  3. Copy the skill directory into a personal or project-level Claude Code skills directory.
  4. Restart or refresh Claude Code so the skill can be discovered.
Verify installation

Ask Claude Code to plan a migration and confirm it starts with a dependency map and characterization tests, not a rewrite.

Prerequisites

  • Code examples are Python; other stacks must be adapted.
  • Traffic shifting and monitoring need infrastructure the skill does not provide.
  • The example percentages and thresholds are illustrative and not validated here.

Example prompts

Representative task

Using the legacy-modernizer skill, plan an incremental migration of our legacy order service to a new service: produce a risk register, rollback plan per phase, a strangler facade and characterization tests.

Inspect before use

Read the legacy-modernizer skill at https://github.com/Jeffallan/claude-skills/blob/67c1961b180dc92cf08983344627109e983e8f51/skills/legacy-modernizer/SKILL.md and its reference files. Explain its workflow, any commands it tells the agent to run, and the main risks before I decide whether to install it.

A decision, with its limits attached

Strengths

  • Every phase has a validation checkpoint.
  • Forbids big-bang rewrites and removing legacy code before the new path is proven.

Considerations

  • Heavy process may be overkill for small systems.
  • Zero-disruption goals require mature monitoring.
Research conclusion

A disciplined migration playbook that favors reversible steps over rewrites.

Traceable by construction

The dossier is a time-bound reading of a public artifact, not an endorsement. Use the source link to inspect the exact upstream material.

Jeffallanclaude-skillsskills/legacy-modernizer
Source type
Community
Commit
67c1961b180dc92cf08983344627109e983e8f51
Collected
20 Nov 2026
Last checked
20 Nov 2026
Upstream license
MIT
Repository stars
12,464
Content basis

Deterministic lexical parsing, YAML frontmatter validation, file inventory, source-described workflow extraction, and heuristic provisional classification of the supplied files only. Generated by machine; no LLM, execution, dynamic testing, or human editorial approval.