cfe-diff

Analyzes 1C configuration extensions for borrowed objects, interceptors, and transfer status.

1|2|Updated Jul 19, 2026
One-click install
npx skills add https://github.com/IngvarConsulting/unica-marketplace --skill cfe-diff-ingvarconsulting
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: cfe-diff
Source: https://github.com/IngvarConsulting/unica-marketplace/tree/main/plugins/unica/skills/cfe-diff
Command: npx skills add https://github.com/IngvarConsulting/unica-marketplace --skill cfe-diff-ingvarconsulting

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Understanding what a 1C:Enterprise configuration extension (CFE) actually contains — which objects are borrowed from the base configuration, which are original, and which method interceptors it defines — normally requires manually inspecting XML dumps. Verifying whether extension insertions were correctly transferred into the target configuration is equally tedious and error-prone. ## Core Features & Use Cases - Extension composition analysis: Lists every object with its kind, name, and status (borrowed, own, missing, or unknownKind), plus per-object counters for attributes, forms, and tabular sections. - Interceptor inspection: Shows each object's modules with their interceptors, including the intercepted method and interception kind. - Transfer verification: Checks whether &ИзменениеИКонтроль insertions were transferred into the configuration, reporting transferred, notTransferred, or needsReview status with reasons. - Use Case: Before merging a vendor extension, run the analysis against your configuration dump to confirm all interceptor insertions were carried over and to see exactly which configuration objects the extension borrows. ## Quick Start Ask the assistant to analyze the extension in src/cfe against the configuration dump in src/cf and report its composition and transfer status.

Frequently Asked Questions about cfe-diff

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

FAQPage Schema
How do I check what a 1C configuration extension contains?▼

Run the cfe-diff analysis with ExtensionPath pointing to the extension dump directory. It returns every object with kind, name, and status (borrowed, own, missing, or unknownKind), plus module interceptors and per-object counters for attributes, forms, and tabular sections.

How to verify extension insertions were transferred into a 1C configuration?▼

Provide both ExtensionPath and ConfigPath dump directories. The transfer field lists each &ИзменениеИКонтроль interceptor with a status of transferred, notTransferred, or needsReview, and needsReview entries always include a reason explaining the finding.

What inputs does the 1C extension analysis require?▼

It requires two mandatory parameters: ExtensionPath, the directory of the extension XML dump, and ConfigPath, the directory of the configuration dump to compare against. Both must be exported configuration sources, not binary cf or cfe files.

Does the extension analysis modify my configuration files?▼

The analysis is read-only reporting of composition and transfer status. For any mutating operation routed through the unica MCP orchestrator, dryRun stays enabled by default and is only disabled when the user explicitly requests the change.

What does a needsReview transfer status mean in 1C extension checks?▼

A needsReview status means the tool could not definitively confirm whether an interceptor insertion was transferred into the configuration. The entry always carries a reason field explaining why manual review is required, so the cause is not lost.