cfe-diff

Analyze 1C Configuration Extensions to enumerate borrowed objects and interceptors.

41|5|Updated May 28, 2026
One-click install
npx skills add https://github.com/msrv-tech/skills --skill cfe-diff-msrv-tech
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cfe-diff
Source: https://github.com/msrv-tech/skills/tree/main/cfe-diff
Command: npx skills add https://github.com/msrv-tech/skills --skill cfe-diff-msrv-tech

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This skill analyzes 1C Configuration Extensions (CFE) to reveal the extension contents, focusing on borrowed objects, interceptors, and the migration status of changes to the base configuration.

Core Features & Use Cases

  • Identifies borrowed vs own objects in the extension and lists their ownership decorations and presence of own items.
  • Extracts interceptors from .bsl scripts for objects, including forms and commands, to illuminate callType behavior.
  • Verifies that changes are transferred to the target configuration by locating insertion blocks (#Вставка) and comparing against the base config.

Quick Start

Launch the cfe-diff tool with -ExtensionPath to the extension folder and -ConfigPath to the base config, then choose Mode A or Mode B to generate the report.

Frequently Asked Questions about cfe-diff

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

FAQPage Schema
How do I analyze 1C CFE extensions for borrowed objects and interceptors?

You can analyze 1C CFE extensions by providing the extension folder and base config path, then choosing Mode A or Mode B to generate a report detailing borrowed objects and interceptors.

What is the process for verifying migration of changes in 1C configuration extensions?

The process verifies migration by locating #Вставка insertion blocks within the extension and comparing them against the base configuration to confirm that changes are properly transferred.

How does extracting interceptors from .bsl scripts work in 1C code review?

Extracting interceptors works by scanning .bsl files for objects, forms, and commands to illuminate callType behavior, which is essential for auditing extension behavior during code review.

Does this 1C extension analysis require a specific base configuration path?

Yes, the analysis requires a base configuration path. You must provide the -ConfigPath argument pointing to the base config alongside the -ExtensionPath argument to generate the report.

Can I use lxml to parse Configuration.xml for 1C CFE auditing?

Yes, you can use lxml to parse Configuration.xml for 1C CFE auditing, as this dependency is required to process XML structures and enumerate borrowed objects with their ownership decorations.