cfe-borrow

Generate adopted object XML metadata and update extension Configuration.xml for 1C CFE borrowing.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill eliminates the manual, error-prone work of duplicating 1C configuration metadata when creating a CFE extension by programmatically “borrowing” selected objects from the base configuration into the extension.

Core Features & Use Cases

  • Object adoption into CFE: Creates per-object XML metadata files in the extension with ObjectBelonging=Adopted and links them via ExtendedConfigurationObject to the source object UUID.
  • Extension Configuration.xml updates: Updates the extension Configuration.xml by adding the borrowed objects into the ChildObjects section with correct ordering and deduplication.
  • Batch borrowing: Accepts multiple objects in one run using the ;; delimiter.
  • Supported scope: Works across many 1C object types (including common types like Catalog, Document, Enum, CommonModule, and more), and ensures required ChildObjects handling for types that need it.

Quick Start

Ask to run /cfe-borrow to borrow Catalog.Контрагенты from ERP configuration into your already-initialized extension at src.

Frequently Asked Questions about cfe-borrow

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

FAQPage Schema
How do I borrow 1C configuration objects into a CFE extension?

You can batch borrow multiple 1C objects into a CFE extension by providing the object names in a single run using the `;;` delimiter. The tool processes each object and updates the extension Configuration.xml accordingly.

What 1C object types can I adopt into a CFE extension?

Borrowing 1C objects into a CFE extension creates per-object XML metadata files with ObjectBelonging=Adopted and links them via ExtendedConfigurationObject to the source object UUID. It also updates the extension Configuration.xml ChildObjects section.

Do I need an initialized CFE extension before borrowing 1C objects?

Borrowing 1C objects into a CFE extension supports patch-creation workflows after cfe-init. It applies when you must intercept methods or adjust forms by first adopting source objects into the extension.

How do I borrow multiple 1C configuration objects into a CFE extension at once?

Batch borrowing 1C objects into a CFE extension requires specifying multiple object names separated by `;;`. The tool reads the source Configuration.xml object XML by type directory mapping and creates UTF-8 XML files under the extension.

Why do I need to adopt 1C objects into a CFE extension?

Adopting 1C objects into a CFE extension eliminates the manual, error-prone work of duplicating configuration metadata. It programmatically creates adopted object XML files with ObjectBelonging=Adopted and updates the extension Configuration.xml.