cfe-borrow

Borrows configuration objects and forms from a 1C configuration into a CFE extension.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Modifying standard 1C:Enterprise configuration objects (catalogs, documents, forms) without touching the base configuration requires manually creating extension XML files with correct ObjectBelonging and ExtendedConfigurationObject references, which is error-prone and tedious. ## Core Features & Use Cases - Object Borrowing: Adopts any of the 44 configuration object types (Catalog, Document, CommonModule, Enum, etc.) into an extension, generating XML with ObjectBelonging=Adopted and registering entries in ChildObjects. - Form Borrowing: Copies managed forms with metadata, Form.xml, Module.bsl, and optional main attribute borrowing (Form or All modes) so new attributes can later be displayed on the adopted form. - Batch Operations: Borrows multiple objects in one call using the ;; separator, with automatic parent-object borrowing and protection against overwriting already-adopted content. - Use Case: You need to add a new attribute to the Контрагенты catalog and show it on its element form: borrow the form with -BorrowMainAttribute, then use /meta-edit and /form-edit to complete the change. ## Quick Start Ask the assistant to borrow the form Catalog.Контрагенты.Form.ФормаЭлемента from your configuration source into your extension directory with main attributes included.

Frequently Asked Questions about cfe-borrow

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

FAQPage Schema
How do I borrow a form from a 1C configuration into an extension?▼

Call the unica.cfe.borrow MCP tool with the Object parameter in the format Type.Name.Form.FormName, for example Catalog.Контрагенты.Form.ФормаЭлемента. The parent object is borrowed automatically if it is not already adopted, and the form metadata, Form.xml, and Module.bsl are created.

How to add a new attribute to an existing 1C configuration object using an extension?▼

First borrow the object's form with the BorrowMainAttribute parameter so the form keeps its data bindings, then add the attribute with /meta-edit and display it with /form-edit. Use BorrowMainAttribute=Form for attributes already on the form or All for every attribute.

Can I borrow multiple 1C configuration objects in one operation?▼

Yes, pass several objects in the Object parameter separated by double semicolons, for example Catalog.X ;; CommonModule.Y ;; Enum.Z. All 44 configuration object types are supported in batch mode.

What happens if an object is already borrowed in the extension?▼

The tool does not overwrite existing adopted content. If a dependent object was already borrowed with attributes or forms, only the missing parts are added, protecting your existing extension data.

What is required before borrowing objects into a 1C extension?▼

The extension must already exist with a valid Configuration.xml, typically created with /cfe-init. The configuration source path can be auto-detected from v8project.yaml by locating the source-set with type CONFIGURATION.