cfe-validate

Validate 1C CFE extension XML structure, metadata, and borrowed objects.

Updated Feb 21, 2026
One-click install
npx skills add https://github.com/mmmmmm786mngb-jpg/WIM_DEV --skill cfe-validate
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cfe-validate
Source: https://github.com/mmmmmm786mngb-jpg/WIM_DEV/tree/main/.cursor/skills/cfe-validate
Command: npx skills add https://github.com/mmmmmm786mngb-jpg/WIM_DEV --skill cfe-validate

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This tool validates the structural integrity and metadata of 1C Configuration Extension (CFE) deployments, catching issues after creation or modification.

Core Features & Use Cases

  • Validates XML structure and metadata in 1C CFE extensions, including Configuration.xml and related properties.
  • Checks internal references, required identifiers, and borrowed object consistency to ensure deployable configurations.
  • Use Case: QA teams verify extension correctness before publishing to production or sharing with customers.

Quick Start

Run the validator against your extension's Configuration.xml or folder to perform a full integrity check.

Frequently Asked Questions about cfe-validate

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

FAQPage Schema
How do I validate a 1C configuration extension before deployment?

Validating a 1C CFE extension involves parsing its Configuration.xml or extension folder to check XML structure, required metadata, and borrowed objects. This process catches structural errors in object IDs, generated types, and language references before deployment.

Why does my 1C CFE extension have structural errors after modification?

Structural errors in a modified 1C CFE often stem from inconsistent borrowed objects, missing required identifiers, or broken internal references. Checking the Configuration.xml and related properties detects these issues before the extension is deployed.

What does checking a 1C CFE extension with lxml actually verify?

Checking a CFE extension with lxml verifies its XML structure, required metadata, and borrowed object consistency. It reports found issues with object IDs, generated types, and language references to ensure a deployable configuration.

Can I use a script to check 1C CFE metadata and generated types?

Yes, you can use a validation script to check 1C CFE metadata and generated types. The script parses Configuration.xml and related properties to report issues with object IDs, generated types, and language references.

Does cfe-validate work with just the extension folder?

Yes, the validator works with just the extension folder. It parses either the Configuration.xml file or the extension folder directly to perform a full integrity check and report any structural issues found.

When should I run a quality assurance check on my 1C CFE?

You should run a quality assurance check on your 1C CFE immediately after creation or modification. This ensures structural integrity and verifies internal references before publishing to production or sharing with customers.