form-validate

Validate 1C managed Form.xml structural integrity and element wiring.

413|90|Updated Aug 31, 2025
One-click install
npx skills add https://github.com/comol/cursor_rules_1c --skill form-validate
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: form-validate
Source: https://github.com/comol/cursor_rules_1c/tree/main/.cursor/source/form-validate
Command: npx skills add https://github.com/comol/cursor_rules_1c --skill form-validate

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Validates the structural correctness of 1C managed Form.xml to prevent runtime errors by enforcing unique IDs, proper companion elements, valid DataPath references, and correct event and command wiring.

Core Features & Use Cases

  • Comprehensive structural checks: root Form version, AutoCommandBar, unique IDs for elements, attributes, and commands.
  • Integrity validation: companion elements, DataPath references, button CommandName references, event handler presence, and command actions.
  • Quick validation after edits: run the validator on generated or edited Form.xml to catch misconfigurations before deployment.

Quick Start

Run the validator against your Form.xml by providing the full path to the file.

Frequently Asked Questions about form-validate

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I validate 1C Form.xml structure to prevent runtime errors?

Validating 1C Form.xml structure requires checking root Form version, AutoCommandBar, unique element IDs, companion elements, DataPath references, and event wiring. The validator returns a clear pass/fail result with actionable feedback.

Can I check 1C managed form event handlers and command wiring in CI?

Yes, you can check 1C managed form event handlers and command wiring in CI. The validator runs deterministically in CI pipelines, verifying event handler presence and command actions to catch misconfigurations before deployment.

What structural issues cause 1C Form.xml runtime errors?

1C Form.xml runtime errors are caused by duplicate element IDs, invalid DataPath references, missing companion elements, and incorrect event or command wiring. The validator enforces unique IDs and proper references to prevent these failures.

Does the validator check for unique IDs across 1C form elements, attributes, and commands?

Yes, the validator checks for unique IDs across 1C form elements, attributes, and commands. It enforces ID uniqueness to ensure structural integrity and prevent reference conflicts within the managed Form.xml.

What's the best way to catch 1C Form.xml misconfigurations after editing?

The best way to catch 1C Form.xml misconfigurations after editing is to run a structural validator on the generated or edited file. It detects invalid DataPath references, broken button CommandName links, and missing companion elements.

Do I need any dependencies to validate 1C managed Form.xml files?

No dependencies are required to validate 1C managed Form.xml files. The validator operates standalone, requiring only the full path to the Form.xml file to perform structural and integrity checks deterministically.