Analyze M1 Module For Migration

Decides migrate/replace/skip for a Magento 1 module before an M2 port

Getestet · Funktioniert ★ 9.6/10

Was es kann

Walks a Magento 1 module through identification, config/DB/file-usage analysis, M2-alternative research, and a weighted decision matrix to produce a migrate/use-alternative/skip recommendation with a stakeholder-ready report. Triggers on deciding whether to migrate, replace, or drop an M1 module during a Magento 1-to-2 migration; explicitly flags 'installed does not mean used' and refuses to guess when production DB access is unavailable.

Testbericht

Built a small synthetic M1 module fixture (observer + custom table) and ran it end to end: the skill-guided report correctly identified the exact event hook and table, then explicitly refused to conclude a migration recommendation because Step 3 (production usage verification) was unavailable — exactly the 'installed does not mean used' discipline it preaches. The ad hoc baseline skipped that check and guessed 'probably safe to skip' instead.

Getestet am: 2026-07-16 · Claude Code 2.x (agent harness)

Installation

git clone https://github.com/ProxiBlue/claude-skills
mkdir -p ~/.claude/skills
cp -r claude-skills/analyze-m1-module-for-migration ~/.claude/skills/analyze-m1-module-for-migration

Befehle & Beispiel-Prompts

/analyze-m1-module-for-migrationDecides migrate/replace/skip for a Magento 1 module before an M2 port

Skills reagieren auf normale Anfragen — keine Slash-Befehle nötig. Nach der Installation aktivieren Prompts wie diese den Skill (auf Englisch):

Should we migrate this Magento 1 module to M2 or just drop it entirely
Analyze whether this legacy M1 observer module is even still being used
Give me a migrate-or-skip recommendation for this Magento 1 module

Vollständiger Testbericht (Englisch) →