interface-validate

Validate 1C CommandInterface.xml structure for root, namespace, sections, and command references.

41|5|Updated May 28, 2026
One-click install
npx skills add https://github.com/msrv-tech/skills --skill interface-validate-msrv-tech
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: interface-validate
Source: https://github.com/msrv-tech/skills/tree/main/interface-validate
Command: npx skills add https://github.com/msrv-tech/skills --skill interface-validate-msrv-tech

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Validates the CommandInterface.xml structure used by 1C subsystems to ensure proper root, namespace and section integrity, preventing misconfigurations that could break interface behavior.

Core Features & Use Cases

  • Validates root element, namespace, and version presence to guarantee baseline correctness.
  • Checks required sections (CommandsVisibility, CommandsPlacement, CommandsOrder, SubsystemsOrder, GroupsOrder) and detects duplicates, ensuring consistent configuration.
  • Verifies command references and ordering across all sections to catch misconfigurations before deployment and during testing.

Quick Start

Run the interface-validate script with the required -CIPath parameter pointing to the CommandInterface.xml to perform a full structural validation.

Frequently Asked Questions about interface-validate

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

FAQPage Schema
How do I validate a 1C CommandInterface.xml file for structural errors?

To validate a 1C CommandInterface.xml file, run the interface-validate script with the CIPath parameter pointing to the file to check root elements, namespaces, sections, and command references.

What specific structural checks are performed during 1C CommandInterface validation?

1C CommandInterface validation checks root elements, namespaces, required sections like CommandsVisibility and CommandsOrder, detects duplicates, and verifies command references and ordering across all defined sections.

Do I need lxml installed to validate my 1C CommandInterface structure?

Yes, you need the lxml library installed as a dependency to run the script that validates the 1C CommandInterface.xml structure for correctness and reports configuration errors.

Why does my 1C CommandInterface validation fail when checking sections and ordering?

1C CommandInterface validation fails when required sections like CommandsPlacement or GroupsOrder are missing, contain duplicates, or have incorrect command ordering, and reports errors with actionable guidance.

Can I check for duplicate commands in 1C CommandInterface.xml before deployment?

Yes, you can check for duplicate commands in 1C CommandInterface.xml before deployment by running a validation script that detects duplicates and verifies command references across all defined sections.

What is the best way to prevent misconfigurations in 1C subsystem interface behavior?

The best way to prevent misconfigurations in 1C subsystem interface behavior is to validate the CommandInterface.xml structure, ensuring proper root, namespace, and section integrity to catch errors before deployment.