skills.rest
Alex1980Alex
Alex1980AlexCOMMUNITY
Explore all skills by this author →
GitHub

cf-validate

Validates 1C configuration XML files for structural and property errors.

Updated Mar 29, 2026
Search Tags:#python#validation#configuration#xml#powershell#1c
One-click install
npx skills add https://github.com/Alex1980Alex/1C-Framework --skill cf-validate-alex1980alex
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: cf-validate
Source: https://github.com/Alex1980Alex/1C-Framework/tree/main/external/cc-1c-skills/.claude/skills/cf-validate
Command: npx skills add https://github.com/Alex1980Alex/1C-Framework --skill cf-validate-alex1980alex

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

It verifies exported 1C configuration metadata so you can catch malformed XML, missing language links, broken object references, and inconsistent properties before runtime.

Core Features & Use Cases

  • Structural validation: Confirms Configuration.xml root, UUIDs, InternalInfo, and required properties.
  • Metadata integrity checks: Validates ChildObjects types, canonical ordering, duplicates, language files, and form references.
  • Practical use case: Run it after editing a configuration export to quickly spot issues that would cause load or deployment failures.

Quick Start

Run the cf-validate skill against your 1C configuration export path to check the Configuration.xml structure and report any 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 files before deployment?▼

You can validate 1C configuration XML by checking the Configuration.xml root structure, InternalInfo, UUIDs, and required properties to catch malformed XML and missing language links before runtime deployment.

What structural errors are commonly found in 1C Configuration.xml exports?▼

Common structural errors in 1C Configuration.xml exports include malformed XML, missing InternalInfo, invalid UUIDs, broken form references, and inconsistent ChildObjects ordering or duplicates within the metadata tree.

Do I need Python and lxml to check 1C metadata integrity?▼

Yes, you need Python and the lxml dependency to run validation scripts that check 1C metadata integrity, including ChildObjects types, canonical ordering, language file presence, and referenced form files.

Can I verify ChildObjects ordering and duplicates in 1C configuration exports?▼

Yes, you can verify ChildObjects ordering and duplicates in 1C configuration exports by running metadata integrity checks that validate canonical ordering, detect duplicates, and confirm correct object types within the metadata tree.

When should I run a validation check on my 1C configuration export?▼

You should run a validation check on your 1C configuration export immediately after editing metadata to quickly spot structural issues, broken references, or missing language files that would cause load or deployment failures.

Related Skills

Explore More Software Engineering Skills→
mmmmmm786mngb-jpgmmmmmm786mngb-jpg

meta-compile

Convert JSON DSL definitions into 1C metadata XML and configuration exports.

Community
Intermediate
Dach-CoinDach-Coin
33

cfe-validate

Validate 1C CFE Configuration.xml structure, metadata, and repository consistency.

Community
Intermediate
IngvarConsultingIngvarConsulting
140

help-add

Generate Help.xml and HTML pages and update 1C form metadata.

Official
Basic
Desko77Desko77
40

1c-cfe-validate

Validate 1C CFE extension XMLs for structural and configuration issues.

Community
Advanced