magento-diagnostic_skill
7
GitHub Stars
1
Bundled Files
2 months ago
Catalog Refreshed
4 months ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstrat where the catalogue uses aiagentskills.
npx veilstrat add skill proxiblue/claude-skills --skill magento-diagnostic- SKILL.md3.0 KB
Overview
This skill performs a comprehensive Magento 2 system diagnostic to speed up troubleshooting and performance tuning. It collects cache and indexer status, module and configuration data, logs, and runtime performance metrics and presents a concise health report. The output highlights critical issues, warnings, and prioritized remediation steps for rapid action.
How this skill works
The skill runs Magento CLI commands and reads key log and database sources to extract system state: deploy mode, versioning, cache backends, indexer modes, module lists, cron and queue status, and recent log entries. It correlates findings into an executive summary, computes a health score, classifies issues by severity, and generates a prioritized action plan. Optional integrations allow deeper database and filesystem analysis for slow queries, table sizes, and log parsing.
When to use it
- Investigating a sudden site outage or critical errors
- Diagnosing performance degradation or slow page loads
- Validating system health before or after a deployment
- Routine health checks and proactive maintenance
- Preparing for Magento upgrades or major module changes
Best practices
- Run diagnostics from the Magento application user with correct file permissions
- Collect reports before and after changes to compare state and impact
- Enable relevant logs (debug only when needed) to avoid noise and performance impact
- Schedule regular checks and archive reports for trend analysis
- Address critical issues first (cron, cron queues, indexer locks, cache misconfiguration)
Example use cases
- Customer reports slow catalog pages: gather cache hit/miss, FPC backend, indexer backlog, and recent exceptions
- Post-deploy validation: confirm deploy mode, module versions, cron executions, and no new error log entries
- Pre-upgrade audit: export module list, custom vs vendor modules, DB version, and table sizes to assess upgrade readiness
- Regular maintenance run: health score, warnings for configuration drift, and a prioritized action plan for the week
FAQ
Typical runs complete in a few seconds to a couple of minutes depending on log sizes and database responsiveness.
Can this run on production safely?
Yes, diagnostics are read-only when run with standard Magento CLI commands and log reads. Avoid enabling verbose debug logging in production while diagnosing.
