Magento Issue Debugger
CheckedThis Magento Issue Debugger helps developers quickly identify and resolve problems within their Magento stores by analyzing logs and providing insights.
Install on your platform
Showing Claude Code. One command installs this skill into any of the agents below.
- 1
Run this in your project
terminal$ npx skills add maxnorm/magento2-agent-skills --skill magento-issue-debugger -a claude-code Uses the open-source
skillsCLI and needs Node.js. Add-gto install it for your user instead of this project.
What we know about this skill
Publisher
maxnorm
Taken from the source listing. We haven't verified who controls this account.
Install target
Live repository
Not pinned. Installing fetches whatever the repository holds at the time you run the command.
Automated safety checks
This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.
Declares what it does: passed
SKILL.md parses and declares a name and a description.
SKILL.md exists, its frontmatter parses, and it declares a name and a description.
No undeclared network calls: passed
Makes no network calls.
Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.
No obfuscated payloads: passed
No encoded or obfuscated payloads.
No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.
No credential access: passed
Reads no keys, tokens, keychains or credential files.
Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.
No pipe-to-shell installers: passed
No pipe-to-shell or download-and-run installers.
No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.
Pinned to a commit: passed
Scanned maxnorm/magento2-agent-skills at b3a20f960d.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.
- Commit
- b3a20f960d
- Scanned
- 1 file, 166 lines
About this skill
The magento-issue-debugger skill is designed to assist AI agents in troubleshooting and resolving specific issues within Magento 2 e-commerce environments. It leverages the platform's diagnostic tools to analyze error logs, configuration files, and system performance metrics to identify root causes.
When to use it
- Diagnosing unexpected checkout failures or payment gateway timeouts during high-traffic periods.
- Investigating database connection errors or slow query performance reported in server logs.
- Resolving theme compatibility issues causing layout breaks on specific product pages.
- Analyzing extension conflicts that result in JavaScript console errors or API request failures.
Key capabilities
- Parses Magento 2 system and var log files to extract relevant error traces.
- Validates XML configuration structures against standard Magento schema requirements.
- Identifies missing dependencies or corrupted cache data contributing to runtime exceptions.
- Correlates specific module versions with known community-reported bugs.
Example prompts
- "Analyze the attached
system.logfile and explain why the 'Add to Cart' button is throwing a 500 error on the frontend." - "Check if the current Magento version is compatible with the installed 'Advanced Shipping Rules' extension based on the provided config.xml."
- "Identify potential causes for the database deadlock occurring during the nightly inventory synchronization process."
Tips & gotchas
Ensure you have full read access to the server's log directories before initiating a diagnostic session, as missing permissions will prevent accurate analysis. This skill focuses on technical troubleshooting and may not resolve issues stemming from incorrect business logic or custom code modifications that require manual patching.