erf-validate

Validate 1C ERF external report XML structure and completeness.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill solves the problem of broken or invalid 1C external report packages by validating ERF XML structure and required components before you try to load them in your project.

Core Features & Use Cases

  • Structural XML validation for ExternalReport ERF: checks root structure, InternalInfo, and key schema elements like MainDataCompositionSchema.
  • Child object and metadata integrity checks: verifies ChildObjects, requisites, and table parts, including uniqueness of names.
  • Completeness verification: ensures referenced files for forms and layouts (when applicable) exist so the report can be safely activated.

Use case: After you generate or modify an ERF external report (for example, by editing its XML sources during a refactor or code generation), run this Skill to confirm it matches the expected structure and avoid runtime loading errors.

Quick Start

Run the validation for your ERF by telling the assistant: "Validate the ERF external report at src/МойОтчет with detailed output and stop after 30 errors."

Frequently Asked Questions about erf-validate

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

FAQPage Schema
How do I validate 1C ERF external report XML before loading it?

Validate 1C ERF external report XML by running schema checks on the ExternalReport package directory or single XML file to verify required sections like InternalInfo, MainDataCompositionSchema, and ChildObjects before deployment.

Why does my 1C external report fail to load after editing XML sources?

1C external reports fail to load when XML lacks structural completeness, missing referenced form files, or duplicate ChildObjects names; validating ERF XML structure catches these errors before runtime loading.

What schema checks are required for 1C ERF ExternalReport packages?

Required ERF schema checks cover root structure, InternalInfo, MainDataCompositionSchema, ChildObjects requisites, tabular parts, unique naming, and presence of referenced form and layout files for complete package validation.

Can I lint a single ERF XML file instead of the full report directory?

Yes, ERF XML linting supports both post-generation and post-edit validation at directory and single-XML-file granularity, allowing you to target individual external report XML files for structural checks.

What is the best way to automate 1C ERF XML validation during a build?

Automate 1C ERF XML validation by running schema checks on generated external report packages to enforce build quality, stopping after a specified error limit for immediate feedback.