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

cfe-diff

Analyze 1C configuration extension dumps for borrowed objects and transferred insertion blocks.

Updated Mar 29, 2026
Search Tags:#code comparison#1c#xml parsing#cfe#extension analysis#form interceptors
One-click install
npx skills add https://github.com/Alex1980Alex/1C-Framework --skill cfe-diff-alex1980alex
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: cfe-diff
Source: https://github.com/Alex1980Alex/1C-Framework/tree/main/external/cc-1c-skills/.claude/skills/cfe-diff
Command: npx skills add https://github.com/Alex1980Alex/1C-Framework --skill cfe-diff-alex1980alex

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill helps you inspect a 1C configuration extension and understand exactly what it changes, which borrowed objects it uses, and whether inserted code has been transferred back into the base configuration.

Core Features & Use Cases

  • Extension overview: Identifies borrowed and own objects, then summarizes interceptors, forms, attributes, and tabular sections.
  • Transfer verification: Checks whether code wrapped in insertion markers has already been copied into the corresponding base configuration modules.
  • Use case: A developer can point the Skill at an extension and a configuration dump to quickly audit customization scope, review forms and call-type handlers, and confirm migration status before release.

Quick Start

Ask the Skill to analyze a 1C extension path and a base configuration path, then report borrowed objects, form callType handlers, and transferred insertion blocks.

Frequently Asked Questions about cfe-diff

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

FAQPage Schema
How do I check if 1C extension insertion blocks have been transferred to the base configuration?▼

To verify 1C extension insertion block transfers, compare the extension modules against the base configuration dump to confirm whether code wrapped in insertion markers has been copied over. This transfer verification identifies migrated customization code before release.

What is the best way to analyze 1C configuration extensions and identify borrowed objects?▼

Analyzing 1C configuration extensions involves inspecting XML module trees to distinguish borrowed objects from own objects. The process summarizes interceptors, forms, attributes, and tabular sections to audit the full customization scope of the CFE.

How does XML parsing work for reviewing 1C form interceptors and callType handlers?▼

XML parsing for 1C form interceptor review uses lxml to inspect parsed Configuration.xml files and object directory mappings. This mechanism compares extension form modules with the base configuration to extract and evaluate callType handlers.

Do I need parsed Configuration.xml files to compare 1C CFE module trees?▼

Yes, comparing 1C CFE module trees requires parsed Configuration.xml files, object directory mappings, and lxml-based XML inspection. These inputs are necessary to evaluate object-level BSL code and form modules against the base configuration.

Can I use lxml to inspect 1C extension dumps and audit customization scope?▼

Yes, you can use lxml to inspect 1C extension dumps and audit customization scope. The library performs XML inspection on configuration extension dumps to reveal borrowed objects, form interceptors, and transferred insertion blocks.

Related Skills

Explore More Software Engineering Skills→
Desko77Desko77
40

1c-meta-remove

Remove metadata objects from 1C configuration dumps via XML and BSL.

Community
Advanced
msrv-techmsrv-tech
41

cfe-diff

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

Community
Intermediate
Alex1980AlexAlex1980Alex

bsl-refactoring-workflow

Classify BSL code changes and select safe rename or edit workflows.

Community
Advanced
msrv-techmsrv-tech
41

ibcmd-1c-builds

Automate 1C configuration builds and extension workflows using ibcmd.

Community
Advanced