meta-remove

Remove metadata objects from 1C configuration XML dumps with reference validation.

41|5|Updated May 28, 2026
One-click install
npx skills add https://github.com/msrv-tech/skills --skill meta-remove-msrv-tech
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: meta-remove
Source: https://github.com/msrv-tech/skills/tree/main/meta-remove
Command: npx skills add https://github.com/msrv-tech/skills --skill meta-remove-msrv-tech

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Безопасно удаляет объект из XML-выгрузки конфигурации 1С. Перед удалением проверяет ссылки на объект в реквизитах, коде и других метаданных, чтобы предотвратить разрушение конфигурации.

Core Features & Use Cases

  • Обеспечение безопасного удаления: если найдены ссылки на объект, удаление блокируется или требует принудительного удаления.
  • Дерегистрация объекта из Configuration.xml и удаление сопутствующих файлов и записей в подсистемах (при отсутствии -DryRun).
  • Поддержка режимов DryRun и Force для контроля и проверки перед выполнением операций.

Quick Start

Укажите целевой объект и запустите навык с параметрами, например -DryRun для безопасной проверки или -Force для принудительного удаления.

Frequently Asked Questions about meta-remove

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

FAQPage Schema
How do I safely remove a metadata object from a 1C configuration dump?

To remove a metadata object from a 1C configuration dump safely, this skill validates references in attributes and code before deregistering it from Configuration.xml and deleting associated files. It enforces safety checks to prevent configuration corruption.

Can I check for broken references in 1C metadata before deleting files?

Yes, you can check for broken references in 1C metadata by running the skill in DryRun mode. This safely reports on existing references and planned changes without actually deregistering the object or deleting any files from the configuration.

How does deregistration from Configuration.xml work for 1C metadata objects?

Deregistration from Configuration.xml works by removing the metadata object's entries and associated subsystem records. After validating that no references remain, the skill updates the XML export and optionally deletes the physical files.

What is the best way to force delete a 1C metadata object with active references?

The best way to force delete a 1C metadata object with active references is using the Force parameter. This overrides safety blocks to deregister the object from Configuration.xml and remove files, bypassing the standard reference validation checks.

Do I need lxml installed to deregister 1C metadata objects from XML exports?

Yes, you need the lxml Python library installed to deregister 1C metadata objects from XML exports. This dependency is required for parsing and updating the Configuration.xml files during the reference validation and removal process.