cf-validate

Validate 1C Configuration.xml XML structure and metadata integrity.

33|8|Updated Mar 6, 2026
One-click install
npx skills add https://github.com/Dach-Coin/claude_rules_1c --skill cf-validate-dach-coin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cf-validate
Source: https://github.com/Dach-Coin/claude_rules_1c/tree/main/.claude/skills/cf-validate
Command: npx skills add https://github.com/Dach-Coin/claude_rules_1c --skill cf-validate-dach-coin

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill helps you detect structural problems in 1С Configuration.xml so you can fix configuration errors before they break build/load steps.

Core Features & Use Cases

  • Validates root XML structure: checks XML well-formedness and required root elements/namespaces/version hints.
  • Verifies key configuration blocks: inspects InternalInfo (expected contained objects/class IDs), Properties (Name, DefaultLanguage, etc.), and ChildObjects integrity.
  • Checks consistency with filesystem layout: spot-checks that expected object directories exist and that language files are present.

Quick Start

Run cf-validate on your exported Configuration.xml directory to get a pass/fail report and details about any detected errors.

Frequently Asked Questions about cf-validate

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

FAQPage Schema
How do I validate 1C Configuration.xml structure after editing?

What is 1C Configuration.xml validation for metadata integrity? It is the process of checking XML well-formedness and verifying required metadata structure like InternalInfo, Properties, and ChildObjects to ensure language, module, and object integrity before build steps.

Can I limit the number of errors reported when checking 1C configuration packages?

Yes, you can limit validation errors by using the optional MaxErrors parameter, which restricts the output volume while enforcing fixed namespace and class-id rules during the configuration package check.

Does the validator check filesystem layout consistency for 1C configuration packages?

What does 1C Configuration.xml validation verify for metadata integrity? It checks XML well-formedness, required root elements, and metadata blocks like InternalInfo, Properties, and ChildObjects to ensure language, module, and object integrity before build steps.

Why does my 1C configuration break during load after editing the XML?

Your 1C configuration may break during load due to structural problems in Configuration.xml, such as missing required metadata, invalid namespaces, or incorrect ChildObjects, which validation detects before build or load steps.