mcpbeat Sign in

Frappe Agent Validator Agent Skill

> 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 code, check script, validate deployment, find bugs, code quality, check my code, is this correct, code review, before deploying, best practices check.

9k tokens
context cost
the whole folder, loaded on every use
4
files
instructions only
0
copies elsewhere
how many repositories repackaged it
158
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/Impertio-Studio/Frappe_Claude_Skill_Package --skill frappe-agent-validator

The instruction itself

33 sections, as written by the author

Frappe Code Validator Agent

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

| Check | Severity | Pattern | Fix |

|-------|----------|---------|-----|

| Import statements | FATAL | import X or from X import Y | Use frappe.utils.X() directly |

| Wrong doc variable | FATAL | self.field or document.field | Use doc.field |

| Wrong event for purpose | ERROR | Validation code in on_update | Move to validate event |

| try/except blocks | WARNING | try: ... except: | Use frappe.throw() for validation |

| No null checks | WARNING | doc.field.lower() | Add if doc.field: guard |

Client Script Checks

| Check | Severity | Pattern | Fix |

|-------|----------|---------|-----|

| Server-side API calls | FATAL | frappe.db.get_value() | Use frappe.call() |

| Missing async handling | FATAL | let x = frappe.call() | Use callback or async/await |

| No refresh after set_value | ERROR | frm.set_value() alone | Add frm.refresh_field() |

| Using cur_frm | WARNING | cur_frm.doc.field | Use frm parameter |

| No form state check | WARNING | Missing __islocal/docstatus | Add state guards |

Controller Checks

| Check | Severity | Pattern | Fix |

|-------|----------|---------|-----|

| self.* in on_update | FATAL | self.field = X in on_update | Use self.db_set() |

| Circular save | FATAL | self.save() in lifecycle hook | Remove self.save() |

| Missing super() | ERROR | Override without super() | Add super().method() |

| v16 extend_doctype_class | ERROR | Missing super() in mixin | ALWAYS call super() first |

| No type annotations | SUGGESTION | Missing type hints (v16) | Add type annotations |

hooks.py Checks

| Check | Severity | Pattern | Fix |

|-------|----------|---------|-----|

| Invalid Python syntax | FATAL | Syntax errors | Fix dict/list structure |

| Wrong event names | FATAL | Typo in event name | Use correct event names |

| Invalid function paths | FATAL | Wrong dotted path | Verify path exists |

| v16-only hooks on v14/v15 | ERROR | extend_doctype_class | Use doc_events instead |

| Missing required_apps | WARNING | No dependency declaration | Add all dependencies |

Ops/Bench Checks

| Check | Severity | Pattern | Fix |

|-------|----------|---------|-----|

| No migrate after hooks | FATAL | hooks.py changed, no migrate | Run bench migrate |

| Wrong bench command syntax | ERROR | Incorrect CLI args | Check frappe-ops-bench |

| Missing backup before upgrade | ERROR | Upgrade without backup | ALWAYS backup first |

| Production without supervisor | WARNING | No process manager | Use supervisor/systemd |

| No SSL in production | WARNING | HTTP-only deployment | Configure SSL/TLS |

DocType JSON Checks

| Check | Severity | Pattern | Fix |

|-------|----------|---------|-----|

| Missing mandatory fields | ERROR | No primary identifier | Add name or autoname |

| Duplicate fieldnames | FATAL | Same fieldname twice | Use unique fieldnames |

| Wrong fieldtype for data | WARNING | Text for short values | Use Data/Small Text |

| No permissions defined | WARNING | Empty permission list | Add 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)

| Check | Severity | Description |

|-------|----------|-------------|

| SQL Injection | CRITICAL | Raw user input in SQL |

| Permission bypass | CRITICAL | Missing permission checks |

| XSS vulnerability | HIGH | Unescaped user input in HTML |

| Sensitive data exposure | HIGH | Logging passwords/tokens |

| Hardcoded credentials | CRITICAL | API keys in source code |

Performance Checks (ALL code types)

| Check | Severity | Description |

|-------|----------|-------------|

| Query in loop | HIGH | frappe.db.* inside for loop |

| Unbounded query | MEDIUM | SELECT without LIMIT |

| Unnecessary get_doc | LOW | get_doc when get_value suffices |

| Missing index | MEDIUM | Filter on non-indexed field |

| No batch commit | HIGH | Commit per record in bulk ops |

Error Handling Checks (ALL code types)

| Check | Severity | Description |

|-------|----------|-------------|

| Silent failures | HIGH | except: pass without logging |

| Missing user feedback | MEDIUM | Errors not shown to user |

| Generic error messages | LOW | "An error occurred" |

| No rollback on failure | HIGH | Partial 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

| Level | Checks | Use When |

|-------|--------|----------|

| Quick | Fatal errors only | Initial scan |

| Standard | + Warnings + Security | Pre-deployment (DEFAULT) |

| Deep | + Suggestions + Performance + Ops | Production 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

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

Client Script: 5-point check

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

Controller: 5-point check

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

hooks.py: 5-point check

  • Valid Python syntax? --> Check
  • Function paths exist? --> Check
  • v16-only hooks marked? --> Check
  • required_apps complete? --> Check
  • Fixture filters present? --> Check

Bench/Ops: 5-point check

  • bench migrate after changes? --> REQUIRED
  • Backup before destructive ops? --> REQUIRED
  • Scheduler enabled? --> Check
  • Workers running? --> Check
  • SSL configured (production)? --> Check

See references/checklists.md for complete checklists.

See references/examples.md for validation examples.

Other skills for the same job

different authors, same section of the catalogue
Fresh Eyes Review
by ComeOnOliver
×1

This skill should be used as a mandatory final sanity check before git commit, PR creation, or declaring work done. Triggers on "commit", "push", "PR", "pull request", "done", "finished", "complete", "ship", "deploy", "ready to merge". Catches security vulnerabilities, logic errors, and business rule bugs that slip through despite passing tests.

4k tokens
Style Audit
by ComeOnOliver
×1

Audits code against CI/CD style rules, quality guidelines, and best practices, then rewrites code to meet standards without breaking functionality. Use this skill after functionality validation to ensure code is not just correct but also maintainable, readable, and production-ready. The skill applies linting rules, enforces naming conventions, improves code organization, and refactors for clarity while preserving all behavioral correctness verified by functionality audits.

10k tokens
Create Implementation Plan
by github
vendor

Create a new implementation plan file for new features, refactoring existing code or upgrading packages, design, architecture or infrastructure.

2k tokens
Mcore Cicd
by NVIDIA
vendor

CI/CD reference for Megatron-LM. Covers CI pipeline structure, PR scope labels, triggering internal GitLab CI (which force-pushes the current branch to a pull-request/BRANCH ref — always dry-run and verify the destination first; never run against shared or protected branches), and CI failure investigation.

4k tokens
Sarif Parsing
by trailofbits

>- Parses and processes SARIF files from static analysis tools like CodeQL, Semgrep, or other scanners. Triggers on "parse sarif", "read scan results", "aggregate findings", "deduplicate alerts", or "process sarif output". Handles filtering, deduplication, format conversion, and CI/CD integration of SARIF data. Does NOT run scans — use the Semgrep or CodeQL skills for that.

8k tokens scripts
Tactical Ddd
by tech-leads-club

Detects anemic domain models, validates and refactors them into rich domain models, and enforces tactical DDD patterns (Entities, Value Objects, Aggregates, Domain Services, Domain Events). Use when the user asks to validate, review, or check domain models or DDD code; detect anemia; refactor domain objects; improve encapsulation; or mentions terms like "anemic model", "rich domain", "aggregate", "value object", "domain event", "ubiquitous language", "is this good DDD", "does this follow DDD", or "check my domain". Do NOT use for module or service boundary design, architectural decomposition, strategic DDD context mapping, or code outside the domain layer (DTOs, controllers, infrastructure adapters).

5k tokens
Ios Redteam Pipeline
by elementalsouls

End-to-end iOS red-team pipeline — IPA acquisition (App Store extraction, TestFlight, enterprise/ad-hoc sideload), class-dump/Hopper/Ghidra static analysis, Info.plist + entitlements + Keychain secret extraction, App Transport Security (ATS) misconfig + certificate-pinning bypass (frida-ios-dump, objection, SSL Kill Switch 2), URL-scheme / Universal Link hijack, exported-service enumeration, Frida runtime instrumentation. Companion to apk-redteam-pipeline for the iOS side of a mobile app catalogue. Use when target has an iOS app (App Store listing, TestFlight link, enterprise MDM distribution), when an IPA URL is found hosted on a web server, or when post-recon mentions "iOS app" / "mobile app" in scope alongside an Apple developer account.

4k tokens
Kql Validator
by Azure

Validate KQL (Kusto Query Language) files used in Azure Quick Review (azqr) against their recommendation definitions. Use when the user wants to validate KQL syntax, check semantic alignment with recommendations, verify property names against Azure REST API schemas, or audit KQL queries before a pull request. WHEN: "validate kql", "check kql files", "kql syntax error", "validate aks kql", "run kql validator", "validate azure resource graph queries", "check recommendations alignment", "validate kql for <service>".

8k tokens

How to use it

Copy the folder

Take impertio-studio/frappe-agent-validator from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.