1c-extensions

Guides annotation selection and directive syntax for 1C:Enterprise configuration extensions.

Updated Jun 26, 2026
One-click install
npx skills add https://github.com/pavelvdo/universal-xml-exchange2 --skill 1c-extensions-pavelvdo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: 1c-extensions
Source: https://github.com/pavelvdo/universal-xml-exchange2/tree/main/.cursor/skills/1c-extensions
Command: npx skills add https://github.com/pavelvdo/universal-xml-exchange2 --skill 1c-extensions-pavelvdo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Modifying standard 1C:Enterprise configuration code through extensions is error-prone: choosing the wrong annotation (&Перед/&После vs &ИзменениеИКонтроль vs &Вместо), breaking bitwise code matching, or losing customizations after a configuration update. This Skill provides a decision tree, syntax rules, and a migration algorithm to make extension changes safely. ## Core Features & Use Cases - Annotation Decision Tree: Select the correct annotation based on whether the target is a procedure or function and whether you need logic before, after, inside, or instead of the standard method. - &ИзменениеИКонтроль Rules: Enforce bitwise-identical standard code outside #Вставка/#Удаление directives, with anti-patterns for refactoring, formatting changes, and misplaced #Область markup. - Update Migration Algorithm: Three-file merge process (old standard, old modified, new standard) using anchor-based directive relocation with conflict flagging. - Use Case: After a vendor configuration update breaks your extension, use the migration algorithm to re-anchor your #Вставка blocks into the new standard procedure without losing customizations. ## Quick Start Ask the assistant to modify a standard 1C procedure in an extension and follow the annotation decision tree to apply the change with the correct directives.

Frequently Asked Questions about 1c-extensions

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

FAQPage Schema
How do I choose between &Перед, &После, &Вместо, and &ИзменениеИКонтроль in 1C extensions?

Use &Перед or &После for adding logic around standard procedures, &ИзменениеИКонтроль for edits inside a method body, and &Вместо with ПродолжитьВызов for conditional replacement. Note that &Перед and &После only work on procedures, never functions.

How to modify standard 1C code inside a procedure using an extension?

Use the &ИзменениеИКонтроль annotation and wrap all changes in #Вставка/#КонецВставки or #Удаление/#КонецУдаления directives. Code outside directives must match the standard configuration bitwise, including whitespace and formatting.

Can I use &Перед or &После annotations on functions in 1C?

No, the 1C platform does not support &Перед and &После on functions, only on procedures. For functions, use &Вместо with ПродолжитьВызов() or &ИзменениеИКонтроль instead.

Why does my 1C extension fail applicability checks after editing?

Applicability fails when code outside #Вставка/#Удаление directives differs from the standard configuration, even by whitespace or renamed variables. It also fails when hook signatures do not exactly match the base procedure's parameters.

How do I migrate extension changes after a 1C configuration update?

Use the three-file algorithm: extract directive blocks from the old modified file, identify anchor lines in standard code, locate those anchors in the new standard version via diff, and reinsert directives. Flag missing anchors as conflicts for manual resolution.