Frappe Code Validator Agent

SkillCloud & infra

Use when reviewing or validating Frappe/ERPNext code against best practices and common pitfalls. Checks generated code before deployment, validates against all 61 frappe-* skills, catches v16 patterns (extend_doctype_class, type annotations), validates ops patterns (bench commands, deployment), and generates correction reports. Keywords: review code, check script, validate deployment, find bugs, code quality, check my code, is this correct, code review, before deploying, best practices check.

Available today. Use it from your connected AI after setup.

Connect ahel once, and every AI you use reads what you have installed.

Then ask your AI: use the Frappe Code Validator Agent skill

What this skill tells your AI

The instructions your AI receives, as published by impertio-studio/frappe_claude_skill_package in skills/source/agents/frappe-agent-validator/SKILL.md and read by ahel’s review.

Validates Frappe/ERPNext code against the complete 61-skill knowledge base, catching errors BEFORE deployment.

Purpose: Catch errors before deployment, not after

When to Use This Agent

CODE VALIDATION TRIGGERS
|
+-- Code has been generated and needs review
|   "Check this Server Script before I save it"
|   --> USE THIS AGENT
|
+-- Code is causing errors
|   "Why isn't this working?"
|   --> USE THIS AGENT
|
+-- Pre-deployment validation
|   "Is this production-ready?"
|   --> USE THIS AGENT
|
+-- Code review for best practices
|   "Can this be improved?"
|   --> USE THIS AGENT
|
+-- Ops/deployment validation
|   "Is my bench setup correct?"
|   --> USE THIS AGENT

Validation Workflow

STEP 1: IDENTIFY CODE TYPE
  Client Script | Server Script | Controller | hooks.py |
  Jinja | Whitelisted | Bench/Ops | DocType JSON

STEP 2: RUN TYPE-SPECIFIC CHECKS
  Apply checklist for identified code type

STEP 3: CHECK UNIVERSAL RULES
  Error handling | Security | Performance | User feedback

STEP 4: VERIFY VERSION COMPATIBILITY
  v14/v15/v16 features | Deprecated patterns

STEP 5: VALIDATE AGAINST SKILL CATALOG
  Cross-reference with relevant frappe-* skills

STEP 6: GENERATE VALIDATION REPORT
  Critical errors | Warnings | Suggestions | Corrected code

See references/workflow.md for detailed steps.

Critical Checks by Code Type

Server Script Checks

CheckSeverityPatternFix
Import statementsFATALimport X or from X import YUse frappe.utils.X() directly
Wrong doc variableFATALself.field or document.fieldUse doc.field
Wrong event for purposeERRORValidation code in on_updateMove to validate event
try/except blocksWARNINGtry: ... except:Use frappe.throw() for validation
No null checksWARNINGdoc.field.lower()Add if doc.field: guard

Client Script Checks

CheckSeverityPatternFix
Server-side API callsFATALfrappe.db.get_value()Use frappe.call()
Missing async handlingFATALlet x = frappe.call()Use callback or async/await
No refresh after set_valueERRORfrm.set_value() aloneAdd frm.refresh_field()
Using cur_frmWARNINGcur_frm.doc.fieldUse frm parameter
No form state checkWARNINGMissing __islocal/docstatusAdd state guards

Controller Checks

CheckSeverityPatternFix
self.* in on_updateFATALself.field = X in on_updateUse self.db_set()
Circular saveFATALself.save() in lifecycle hookRemove self.save()
Missing super()ERROROverride without super()Add super().method()
v16 extend_doctype_classERRORMissing super() in mixinALWAYS call super() first
No type annotationsSUGGESTIONMissing type hints (v16)Add type annotations

hooks.py Checks

CheckSeverityPatternFix
Invalid Python syntaxFATALSyntax errorsFix dict/list structure
Wrong event namesFATALTypo in event nameUse correct event names
Invalid function pathsFATALWrong dotted pathVerify path exists
v16-only hooks on v14/v15ERRORextend_doctype_classUse doc_events instead
Missing required_appsWARNINGNo dependency declarationAdd all dependencies

Ops/Bench Checks

CheckSeverityPatternFix
No migrate after hooksFATALhooks.py changed, no migrateRun bench migrate
Wrong bench command syntaxERRORIncorrect CLI argsCheck frappe-ops-bench
Missing backup before upgradeERRORUpgrade without backupALWAYS backup first
Production without supervisorWARNINGNo process managerUse supervisor/systemd
No SSL in productionWARNINGHTTP-only deploymentConfigure SSL/TLS

DocType JSON Checks

CheckSeverityPatternFix
Missing mandatory fieldsERRORNo primary identifierAdd name or autoname
Duplicate fieldnamesFATALSame fieldname twiceUse unique fieldnames
Wrong fieldtype for dataWARNINGText for short valuesUse Data/Small Text
No permissions definedWARNINGEmpty permission listAdd role permissions

v16 Specific Validations

extend_doctype_class Pattern

# VALIDATE: Mixin class MUST call super()
class CustomSalesInvoice(SalesInvoice):
    def validate(self):
        super().validate()       # REQUIRED - never skip
        self.custom_validation()

    def on_submit(self):
        super().on_submit()      # REQUIRED - never skip
        self.custom_on_submit()

Type Annotations (v16 best practice)

# v16 recommended pattern
def get_customer_balance(customer: str) -> float:
    ...

# Validate: type hints on public API methods
@frappe.whitelist()
def process_order(order_name: str, action: str = "approve") -> dict:
    ...

Data Masking (v16)

# Validate: sensitive fields should use data masking
# Check if PII fields have mask_with configured in DocType JSON

Universal Validation Rules

Security Checks (ALL code types)

CheckSeverityDescription
SQL InjectionCRITICALRaw user input in SQL
Permission bypassCRITICALMissing permission checks
XSS vulnerabilityHIGHUnescaped user input in HTML
Sensitive data exposureHIGHLogging passwords/tokens
Hardcoded credentialsCRITICALAPI keys in source code

Performance Checks (ALL code types)

CheckSeverityDescription
Query in loopHIGHfrappe.db.* inside for loop
Unbounded queryMEDIUMSELECT without LIMIT
Unnecessary get_docLOWget_doc when get_value suffices
Missing indexMEDIUMFilter on non-indexed field
No batch commitHIGHCommit per record in bulk ops

Error Handling Checks (ALL code types)

CheckSeverityDescription
Silent failuresHIGHexcept: pass without logging
Missing user feedbackMEDIUMErrors not shown to user
Generic error messagesLOW"An error occurred"
No rollback on failureHIGHPartial data on error

Validation Report Format

ALWAYS generate reports in this format:

## Code Validation Report

### Code Type: [type]
### Target: [DocType / App / File]
### Event/Trigger: [if applicable]

### CRITICAL ERRORS (Must Fix)
| # | Line | Issue | Fix |
|---|------|-------|-----|

### WARNINGS (Should Fix)
| # | Line | Issue | Recommendation |
|---|------|-------|----------------|

### SUGGESTIONS (Nice to Have)
| # | Line | Suggestion |
|---|------|------------|

### Corrected Code
[If critical errors found, provide corrected version]

### Version Compatibility
| Version | Status | Notes |
|---------|--------|-------|
| v14 | [status] | |
| v15 | [status] | |
| v16 | [status] | |

### Referenced Skills
- frappe-skill-name: [what was validated against]

Validation Depth Levels

LevelChecksUse When
QuickFatal errors onlyInitial scan
Standard+ Warnings + SecurityPre-deployment (DEFAULT)
Deep+ Suggestions + Performance + OpsProduction review

Skill Catalog Cross-Reference

This validator validates against ALL 61 frappe-* skills:

Syntax Validation (11 skills)

frappe-syntax-clientscripts, frappe-syntax-serverscripts, frappe-syntax-controllers, frappe-syntax-hooks, frappe-syntax-hooks-events, frappe-syntax-whitelisted, frappe-syntax-jinja, frappe-syntax-scheduler, frappe-syntax-customapp, frappe-syntax-doctypes, frappe-syntax-reports

Implementation Validation (12 skills)

frappe-impl-clientscripts, frappe-impl-serverscripts, frappe-impl-controllers, frappe-impl-hooks, frappe-impl-whitelisted, frappe-impl-jinja, frappe-impl-scheduler, frappe-impl-customapp, frappe-impl-reports, frappe-impl-workflow, frappe-impl-website, frappe-impl-ui-components, frappe-impl-integrations

Error Pattern Validation (7 skills)

frappe-errors-clientscripts, frappe-errors-serverscripts, frappe-errors-controllers, frappe-errors-hooks, frappe-errors-api, frappe-errors-permissions, frappe-errors-database

Core Pattern Validation (7 skills)

frappe-core-database, frappe-core-permissions, frappe-core-api, frappe-core-workflow, frappe-core-notifications, frappe-core-files, frappe-core-cache

Ops Validation (8 skills)

frappe-ops-bench, frappe-ops-deployment, frappe-ops-backup, frappe-ops-performance, frappe-ops-upgrades, frappe-ops-cloud, frappe-ops-app-lifecycle, frappe-ops-frontend-build

Testing Validation (2 skills)

frappe-testing-unit, frappe-testing-cicd

Quick Validation Commands

Server Script: 5-point check

  1. Any import statements? --> FATAL
  2. Any self. references? --> FATAL (use doc.)
  3. Any try/except? --> WARNING (usually wrong)
  4. Uses frappe.throw() for validation? --> GOOD
  5. Uses doc.field for access? --> GOOD

Client Script: 5-point check

  1. Any frappe.db.* calls? --> FATAL
  2. Any frappe.get_doc() calls? --> FATAL
  3. frappe.call() without callback? --> FATAL
  4. Uses frm.doc.field for access? --> GOOD
  5. Uses frm.refresh_field() after changes? --> GOOD

Controller: 5-point check

  1. Modifying self.* in on_update? --> FATAL
  2. Missing super().method() calls? --> ERROR
  3. self.save() in lifecycle hook? --> FATAL
  4. Imports at top of file? --> GOOD
  5. Error handling for external calls? --> GOOD

hooks.py: 5-point check

  1. Valid Python syntax? --> Check
  2. Function paths exist? --> Check
  3. v16-only hooks marked? --> Check
  4. required_apps complete? --> Check
  5. Fixture filters present? --> Check

Bench/Ops: 5-point check

  1. bench migrate after changes? --> REQUIRED
  2. Backup before destructive ops? --> REQUIRED
  3. Scheduler enabled? --> Check
  4. Workers running? --> Check
  5. SSL configured (production)? --> Check

See references/checklists.md for complete checklists. See references/examples.md for validation examples.

Signals

GitHub stars
178
Forks
53
Last commit
Jul 2026
Advanced
Catalog kind
skill
Gateway key
frappe-agent-validator
Source
github.com/impertio-studio/frappe_claude_skill_package