What problem does it solve?
It eliminates wasted trial-and-error debugging when Frappe/ERPNext fails in ways that look correct but break in production, such as misleading tracebacks, silent failures, or background-job errors.
Core Features & Use Cases
- Error classification & mechanism detection: Systematically identifies whether an issue is Python, JavaScript, database, permission, hook, scheduler, or build related, then maps it to the likely Frappe mechanism (controller, server script, client script, hook, scheduler, API, build pipeline).
- Evidence-first investigation: Guides you to use bench console, frappe.logger, browser DevTools, and the Error Log DocType to find the decisive evidence rather than guessing.
- Deterministic diagnosis checklists: Applies targeted checklists for each error class (common patterns, likely causes, and safe remediation steps) and ends by producing a fix plus verification steps.
- Use case: When a Sales Invoice submit fails with an ImportError or when a scheduled task runs but does nothing, this Skill provides a step-by-step path to identify the failing code path, the correct logs/tables to inspect, and the precise fix to apply.
Quick Start
When you see a failing request or traceback, tell the AI to classify the error, identify the mechanism, point to the relevant Frappe logs/files/bench commands, and produce a corrected fix with verification steps.
