cfe-diff

Compare 1C configuration extension objects and verify #Вставка block transfers.

151|20|Updated Feb 11, 2026
One-click install
npx skills add https://github.com/Arman-Kudaibergenov/1c-ai-development-kit --skill cfe-diff-arman-kudaibergenov
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: cfe-diff
Source: https://github.com/Arman-Kudaibergenov/1c-ai-development-kit/tree/main/.claude/skills/cfe-diff
Command: npx skills add https://github.com/Arman-Kudaibergenov/1c-ai-development-kit --skill cfe-diff-arman-kudaibergenov

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill helps you analyze a 1C configuration extension (CFE) by identifying borrowed vs own objects and verifying whether required insertion blocks (#Вставка…#КонецВставки) are actually transferred into the target configuration modules.

Core Features & Use Cases

  • Mode A: Extension overview: Lists borrowed and own objects from the extension’s Configuration.xml, including interceptors found in extension .bsl files for key macro methods (&Перед/&После/&ИзменениеИКонтроль/&Вместо) and a quick count of owned child items (attributes, tabular sections, forms).
  • Mode B: Transfer check: For each borrowed object’s &ИзменениеИКонтроль interceptors, extracts #Вставка blocks from the extension .bsl and checks whether the corresponding code blocks exist in the matching modules’ Configuration in ConfigPath.
  • Use Case: Before deploying an extension to production, use Mode B to catch missing transferred insertion code early (status: [TRANSFERRED], [NOT_TRANSFERRED], or [NEEDS_REVIEW]).

Quick Start

Run the skill in Mode B to verify that all #Вставка blocks for &ИзменениеИКонтроль interceptors are present in the target Configuration.xml modules.

Frequently Asked Questions about cfe-diff

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

FAQPage Schema
How do I verify #Вставка blocks are transferred to a 1C configuration before deployment?▼

To verify #Вставка block transfer for a 1C configuration, compare the extension's .bsl interceptors against the target ConfigPath modules to confirm code presence and report deployment readiness.

What is a 1C configuration extension diff analysis and when do I need it?▼

A 1C configuration extension diff analysis identifies borrowed versus own objects and validates interceptor code transfer. You need it during pre-release audits to ensure production readiness before deployment.

How do I check &ИзменениеИКонтроль interceptors in 1C extension .bsl modules?▼

To check &ИзменениеИКонтроль interceptors, scan extension .bsl files for macro methods, extract #Вставка blocks, and match the normalized code against the target Configuration.xml modules.

Does the 1C extension transfer check work without resolving Configuration.xml files?▼

No, the 1C extension transfer check requires resolving ExtensionPath and ConfigPath Configuration.xml files to read ChildObjects and accurately match borrowed object interceptors.

Why does my 1C extension diff return a NEEDS_REVIEW status for insertion blocks?▼

A NEEDS_REVIEW status occurs during 1C extension diff analysis when normalized code matching between #Вставка blocks and target modules yields partial or ambiguous results requiring manual inspection.

Can I list borrowed and own objects from a 1C CFE extension overview?▼

Yes, you can list borrowed and own objects from a 1C CFE extension by reading Configuration.xml ChildObjects and scanning .bsl files to count owned child items and interceptors.