meta-remove

Remove metadata objects from 1C configuration dumps with reference checks.

Updated Feb 21, 2026

Search Tags:#metadata #xml #remove #subsystems #1c #bsl #configuration-dump

Ready to run

npx skills add https://github.com/mmmmmm786mngb-jpg/WIM_DEV --skill meta-remove

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: meta-remove
Source: https://github.com/mmmmmm786mngb-jpg/WIM_DEV/tree/main/.cursor/skills/meta-remove
Command: npx skills add https://github.com/mmmmmm786mngb-jpg/WIM_DEV --skill meta-remove

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Remove a metadata object from a 1C configuration dump safely. It checks for references across XML exports and BSL sources before deregistering the object to prevent broken configurations.

Core Features & Use Cases

Safely remove a metadata object from the dumped configuration (Configuration.xml) and related subsystem entries.
Perform reference checks across XML files and BSL scripts to avoid orphaned references; supports -DryRun to simulate changes and -KeepFiles to preserve deleted artifacts.
Handle multi-type objects (Catalog, Document, Enum, InformationRegister, etc.) and clean up associated files if desired.

Quick Start

Run /meta-remove <ConfigDir> -Object <Type.Name> to remove the specified metadata object from the configuration dump.

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 safely remove a metadata object from a 1C configuration dump, use the meta-remove command with the configuration directory and target object type. It deregisters the object from Configuration.xml, updates Subsystems, checks XML and BSL references, and deletes related files unless kept.

Can I check for XML and BSL references before deleting a 1C metadata object?▼

Yes, you can check for XML and BSL references before deleting a 1C metadata object by running the command with the -DryRun option. This simulates the removal process and reports potential orphaned references without applying any actual changes to your files.

Does removing configuration metadata from Configuration.xml also update 1C Subsystems?▼

Yes, removing configuration metadata from Configuration.xml also updates 1C Subsystems. The tool automatically searches across XML sources and deregisters the removed object from related Subsystems content to prevent broken configurations and orphaned references.

How do I delete a 1C metadata object but keep the associated files?▼

To delete a 1C metadata object but keep the associated files, use the -KeepFiles option when running the removal command. This deregisters the object from Configuration.xml and Subsystems while preserving the original artifacts on disk.

What 1C metadata types are supported when removing objects from a configuration dump?▼

The tool supports removing multi-type 1C metadata objects from a configuration dump, including Catalog, Document, Enum, and InformationRegister. You must provide a valid object type and name, such as Catalog.Товары, to target the specific metadata for removal.

What is the best way to force remove a metadata object from a 1C configuration without reference checks?▼

The best way to force remove a metadata object from a 1C configuration without standard reference checks is by using the -Force option. This bypasses safety validations and directly deregisters the object from Configuration.xml and deletes related files.