subsystem-validate

Validate 1C subsystem XML files against the official metadata schema.

Updated Feb 21, 2026

Search Tags:#automation #config #quality-assurance #xml #validate #subsystem #1c

Ready to run

npx skills add https://github.com/mmmmmm786mngb-jpg/WIM_DEV --skill subsystem-validate

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: subsystem-validate
Source: https://github.com/mmmmmm786mngb-jpg/WIM_DEV/tree/main/.cursor/skills/subsystem-validate
Command: npx skills add https://github.com/mmmmmm786mngb-jpg/WIM_DEV --skill subsystem-validate

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires lxml, and includes scripts (resource) components.

What problem does it solve?

Validation of 1C subsystem XML structures to catch structural and semantic errors early in development or deployment.

Core Features & Use Cases

XML well-formedness and root structure validation for MetaDataObject/Subsystem and its uuid.
Comprehensive property checks for the required fields (Name, Synonym, Comment, IncludeHelpInContents, IncludeInCommandInterface, UseOneCommand, Explanation, Picture, Content) plus content item formatting and boolean value validation.
Cross-file consistency checks including ChildObjects entries, duplicates, existence of referenced Subsystem files, and optional CommandInterface.xml verification.
Use Case: validate a newly created or modified 1C subsystem before packaging or deployment to catch structural or semantic errors early.

Quick Start

Run the validator against a Subsystem XML file to verify its structure and properties.

Frequently Asked Questions about subsystem-validate

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

FAQPage Schema

How do I validate 1C subsystem XML files for structural correctness?▼

To validate 1C subsystem XML, run the provided PowerShell and Python scripts to parse MetaDataObject structures, check required properties, and verify content item formats against the official schema. The validator catches structural and semantic errors early in development or deployment.

What properties does 1C subsystem XML validation check?▼

1C subsystem XML validation checks required properties including Name, Synonym, Comment, IncludeHelpInContents, UseOneCommand, Explanation, Picture, and Content. It also verifies boolean values, content item formatting, and ChildObjects entries for single- and multi-subsystem configurations.

Can I validate cross-file consistency across multiple 1C subsystem configurations?▼

Yes, cross-file consistency validation checks ChildObjects entries, detects duplicates, verifies existence of referenced Subsystem files, and optionally validates CommandInterface.xml. This covers both single- and multi-subsystem configurations across the 1C metadata structure.

Do I need lxml to validate 1C subsystem XML structures?▼

Yes, lxml is a required dependency for validating 1C subsystem XML structures. The Python scripts rely on lxml to perform XML parsing, property checks, content validation, and cross-file existence checks during the validation process.

Why does my 1C subsystem XML fail validation before deployment?▼

1C subsystem XML fails validation when root structure is malformed, required properties like Name or Synonym are missing, content item formats are incorrect, or cross-file references to ChildObjects and Subsystem files are broken. The validator identifies these errors before packaging or deployment.

When should I validate 1C subsystem XML metadata?▼

Validate 1C subsystem XML when creating or modifying a subsystem before packaging or deployment. Early validation catches structural errors, missing required properties, malformed content items, and cross-file inconsistencies before they cause deployment failures.