interface-validate

Validate 1C CommandInterface.xml structure, sections, ordering, and command references.

33|8|Updated Mar 6, 2026

Search Tags:#code quality #validation #xml #subsystem #1c #command interface #configuration checks

Ready to run

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

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill helps you detect structural and ordering issues in 1C CommandInterface.xml files before they cause runtime errors or broken command UI behavior.

Core Features & Use Cases

XML structural validation: verifies root element, allowed sections, and section ordering for CommandInterface.
Command reference checks: validates command identifiers against expected naming patterns.
Duplicate detection: flags duplicated sections and duplicate entries in key ordering/visibility blocks.
Use case: after configuring command interfaces for a subsystem (e.g., for “Sales”), run validation to confirm CommandsVisibility/CommandsPlacement/CommandsOrder and related order lists are consistent.

Quick Start

Run interface-validate on your subsystem’s CommandInterface.xml to get an errors-and-warnings report and fail fast if the XML structure is incorrect.

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 checks for XML well-formedness, root namespace correctness, allowed sections, and required section ordering to detect structural issues and prevent runtime command UI errors.

What causes broken command UI behavior in 1C subsystem configurations?▼

Broken command UI behavior in 1C subsystem configurations is caused by structural and ordering issues in CommandInterface.xml, such as incorrect section names, missing required nodes, or inconsistent CommandsVisibility and CommandsPlacement blocks.

How do I check for duplicate entries in 1C CommandsOrder and CommandsVisibility blocks?▼

Checking for duplicate entries in 1C CommandsOrder and CommandsVisibility blocks involves validating key ordering and visibility structures to flag duplicated sections and ensure command reference formats match expected naming patterns.

Does 1C CommandInterface.xml validation require specific section ordering rules?▼

1C CommandInterface.xml validation requires specific section ordering rules, enforcing correct section names, proper ordering, presence of required nodes, and detection of duplicates to ensure subsystem UI command configurations are structurally correct.

Can I validate command reference identifiers against expected naming patterns in 1C?▼

You can validate command reference identifiers in 1C by checking command identifiers against expected naming patterns, ensuring that CommandsVisibility, CommandsPlacement, and CommandsOrder references are consistently formatted and correctly matched.

When do I need to validate CommandInterface.xml for a 1C subsystem?▼

You need to validate CommandInterface.xml for a 1C subsystem after configuring command interfaces, such as for a Sales subsystem, to confirm that ordering lists and command visibility blocks are consistent before deployment.