frappe-agent-validator

To validate Frappe code, run a validator against your codebase to check server scripts, client scripts, controllers, hooks.py, and Jinja templates. It generates a Markdown report with critical errors, warnings, and suggested fixes for v14–v16 environments.

Frappe code validation prevents production defects by enforcing best practices, scanning for known pitfalls, and ensuring version compatibility. It cross-checks code against a 60-skill catalog to identify security and quality issues across v14–v16 environments.

Yes, the Frappe validator works with ERPNext client scripts and Jinja templates. It also validates server scripts, controllers, and hooks.py across Frappe v14–v16 environments to ensure comprehensive code quality and security coverage.

Yes, you can check ERPNext code compatibility across Frappe versions 14 to 16. The validator performs version compatibility checks and cross-skill validation to ensure your code functions correctly across different framework versions.

The best way to automate Frappe code review for deployment workflows is using an automated validator that cross-checks code against a 60-skill catalog. It produces a detailed Markdown report with critical errors, warnings, and actionable fixes.

Frappe server scripts often have security issues after deployment due to known pitfalls and unenforced best practices. Running a pre-deployment validator identifies these issues beforehand by cross-checking code against a 60-skill catalog.