Analyze M1 Module For Migration

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

Tested · Works

Test report

Verdict
Tested · Works
Score
9.6/10
Tested
Jul 16, 2026
Environment
Claude Code 2.x (agent harness)
Upstream re-checked
Aug 10, 2026 · 868972e

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.

Scored on four weighted criteria — install, triggering, output vs. baseline, docs. How scoring works

  • Installs cleanly 5/5
  • Triggers reliably 5/5
  • Output vs. baseline 9/10
  • Docs & honesty 5/5

What Analyze M1 Module For Migration does

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.

How to install Analyze M1 Module For Migration

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

Skills live in ~/.claude/skills/ (global) or .claude/skills/ (per-project). Restart Claude Code after installing.

Commands — how to trigger Analyze M1 Module For Migration

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

It also activates on plain-language prompts like these:

  • 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

Frequently asked questions

Is the Analyze M1 Module For Migration skill free?
Yes. The skill itself is free from ProxiBlue/claude-skills. SkillProof publishes the install command and an independent test verdict at no cost.
Does Analyze M1 Module For Migration work with Claude Code?
We tested it with Claude Code 2.x (agent harness) on Jul 16, 2026. Verdict: Tested · Works. 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.
What is the Analyze M1 Module For Migration SkillProof Score?
9.6/10 — installs cleanly 5/5, triggers reliably 5/5, output vs. baseline 9/10, docs & honesty 5/5.
How do I install Analyze M1 Module For Migration?
Copy the install command from this page, run it in your terminal, and restart Claude Code. Skills live in ~/.claude/skills/ (global) or .claude/skills/ inside a project.
Can I use Analyze M1 Module For Migration with Cursor, Copilot, Gemini CLI, Codex or other AI tools?
The SKILL.md format is native to Claude (Claude Code, Desktop, claude.ai). The instructions inside adapt to other assistants: Cursor rules, GitHub Copilot instructions, Windsurf rules, Custom GPTs, AGENTS.md for OpenAI Codex, and GEMINI.md for Google Gemini CLI — our conversion guides cover each, and the free converter on the tools page does the wrapping for you.