form-validate

Validate 1C managed form Form.xml for structural errors and ID integrity.

33|8|Updated Mar 6, 2026

Search Tags:#xml validation #1c managed form #DataPath #callType #companion elements #command references #extension checks

Ready to run

npx skills add https://github.com/Dach-Coin/claude_rules_1c --skill form-validate-dach-coin

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: form-validate
Source: https://github.com/Dach-Coin/claude_rules_1c/tree/main/.claude/skills/form-validate
Command: npx skills add https://github.com/Dach-Coin/claude_rules_1c --skill form-validate-dach-coin

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill removes guesswork when a 1C managed form (Form.xml) breaks runtime loading or design-time validation by automatically checking common structural inconsistencies.

Core Features & Use Cases

Form.xml structural validation: checks root element/version, required UI structure, and internal integrity.
ID integrity checks: detects duplicate element IDs, duplicate attribute/command IDs, and validates unique ID pools.
Extension-aware checks: when BaseForm is present, validates callType values and warns about extension-added IDs that fall below the expected range.
DataPath and command reference checks: verifies DataPath roots against defined Attributes and ensures Button command references exist in Commands.
Use case: after creating or modifying a managed form, run this Skill to catch XML-level issues before committing or integrating the form into your 1C project.

Quick Start

Ask the AI to run form-validate on your managed form XML by providing the Form.xml path you want to verify.

Frequently Asked Questions about form-validate

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

FAQPage Schema

How do I validate a 1C managed form Form.xml for structural errors?▼

To validate a 1C managed form Form.xml, parse the XDTO file with v8/1C namespaces and run deterministic checks for missing companion elements, duplicate IDs, and invalid DataPath references to ensure structural consistency before committing.

Why does my 1C managed form fail runtime loading after modifying form extensions?▼

Your 1C managed form may fail runtime loading due to structural inconsistencies like invalid callType values, extension-added IDs falling below expected ranges, or duplicate attribute IDs that violate the required UI structure integrity.

What causes invalid DataPath references in 1C managed forms?▼

Invalid DataPath references in 1C managed forms occur when DataPath roots do not match defined Attributes, or when Button command references point to commands that do not exist in the Commands pool, breaking internal XML integrity.

Can I check callType values and multilingual titles in 1C form extensions?▼

Yes, you can check callType values and multilingual title structures in 1C form extensions by validating the BaseForm presence and executing bounded error reporting via MaxErrors to verify extension-aware consistency.

Are there limitations when checking duplicate IDs in 1C managed forms?▼

Duplicate ID checks in 1C managed forms are bounded by the MaxErrors limit for deterministic error reporting, meaning validation stops reporting once the maximum error threshold is reached during the XML parsing process.