magento-diagnostic

Collect Magento 2 health and configuration data into a structured diagnostic report.

15|1|Updated Oct 24, 2025

Search Tags:#logs #CLI #cache #diagnose #system health #Magento 2

Ready to run

npx skills add https://github.com/ProxiBlue/claude-skills --skill magento-diagnostic

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: magento-diagnostic
Source: https://github.com/ProxiBlue/claude-skills/tree/main/magento-diagnostic
Command: npx skills add https://github.com/ProxiBlue/claude-skills --skill magento-diagnostic

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates comprehensive Magento 2 system diagnostics to speed troubleshooting by surfacing health, performance, and configuration insights.

Core Features & Use Cases

System Status Check: Deploy mode, Magento/PHP versions, database connection, and filesystem permissions.
Cache, Index, and Module Analysis: Review cache state, FPC, indexer status, enabled modules, and dependencies.
Configuration & Logs Review: Collect critical config values and logs (system/exception) for rapid diagnosis.
Performance Metrics: Gather resource usage, cron status, and database sizes.
Use Case: Before an upgrade, run diagnostics to verify compatibility and identify potential blockers.

Quick Start

Use the Magento CLI to perform a full diagnostic: bin/magento deploy:mode:show bin/magento cache:status bin/magento indexer:status tail -n 100 var/log/system.log tail -n 100 var/log/exception.log

Frequently Asked Questions about magento-diagnostic

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I run a full Magento 2 system health diagnostic?▼

Run a Magento 2 diagnostic by executing CLI commands to gather cache status, indexer status, module lists, and recent system logs. This aggregates configuration, performance, and health metrics into a structured report with actionable recommendations.

What does a Magento 2 health check include for troubleshooting?▼

A Magento 2 health check reviews deploy mode, PHP versions, database connections, cache states, indexer status, cron schedules, and filesystem permissions, collecting critical configuration values and tailing exception logs to accelerate issue diagnosis.

Can I use Magento CLI diagnostics before a store upgrade or migration?▼

Yes, running Magento CLI diagnostics before an upgrade verifies compatibility and identifies potential blockers by checking enabled modules, dependencies, and current system configurations across live stores and development environments.

What is the best way to check Magento 2 cache and indexer status?▼

Check Magento 2 cache and indexer status by running bin/magento cache:status and bin/magento indexer:status, which surface FPC state, cache validity, and indexer backlogs to detect performance bottlenecks.

Why is my Magento 2 store slow, and how do I gather performance metrics?▼

Gather Magento 2 performance metrics by checking resource usage, cron status, database sizes, and system logs via CLI. This surfaces indexer backlogs, cache issues, and configuration errors that commonly cause store slowdowns.

Does Magento 2 diagnostic reporting work on both live stores and dev environments?▼

Yes, Magento 2 diagnostic reporting executes system checks and gathers CLI-based metrics across live stores, development environments, and migrations, outputting a structured health report with an executive summary and identified issues.