skills.rest
Alex1980Alex
Alex1980AlexCOMMUNITY
Explore all skills by this author →
GitHub

meta-remove

Remove 1C metadata objects from configuration dumps with XML and BSL reference scanning.

Updated Mar 29, 2026
Search Tags:#metadata#xml#deletion#1c#bsl#reference-checking
One-click install
npx skills add https://github.com/Alex1980Alex/1C-Framework --skill meta-remove-alex1980alex
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: meta-remove
Source: https://github.com/Alex1980Alex/1C-Framework/tree/main/external/cc-1c-skills/.claude/skills/meta-remove
Command: npx skills add https://github.com/Alex1980Alex/1C-Framework --skill meta-remove-alex1980alex

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Removes a 1C metadata object from a configuration dump without leaving stale registrations behind, reducing the risk of broken references and unsafe manual cleanup.

Core Features & Use Cases

  • Reference-aware deletion: Scans XML and BSL files for object references before removal and blocks the operation unless you explicitly force it.
  • Support-state protection: Checks whether the object is under vendor support or locked and stops unsafe edits that could break future updates.
  • Configuration cleanup: Removes the object from Configuration.xml, subsystem content, and the object’s own files or directory.
  • Use Case: Use it when you need to retire an obsolete catalog, document, report, or common module from a 1C configuration export.

Quick Start

Ask the meta-remove skill to delete a specific 1C metadata object from the given configuration directory and tell it whether to dry-run, force removal, or keep files.

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 1C metadata object, scan XML and BSL files for references and clear subsystem registrations before deletion. This skill automates that cleanup to prevent broken references in your configuration.

What happens if there are existing references to a 1C metadata object I want to delete?▼

Reference-aware deletion blocks the operation if it detects existing references in your XML or BSL files. You must resolve these dependencies or explicitly use the force removal option to override the safety check.

Can I check for broken references before actually deleting a 1C metadata object?▼

Yes, you can use the dry-run control to simulate the deletion process. This allows you to identify potential broken references and review configuration changes without permanently altering your XML and BSL files.

Does this metadata deletion tool work with vendor-supported or locked 1C configurations?▼

Support-state protection checks whether the 1C metadata object is under vendor support or locked. It stops unsafe edits that could break future updates, requiring explicit force removal to override these protections.

Do I need Python and lxml to process 1C configuration XML files for cleanup?▼

Yes, processing 1C configuration XML files requires PowerShell or Python execution with lxml-based file parsing. The lxml dependency is necessary to scan sources and manage the metadata object removal workflow.

Related Skills

Explore More Software Engineering Skills→
Alex1980AlexAlex1980Alex

cfe-diff

Analyze 1C configuration extension dumps for borrowed objects and transferred insertion blocks.

Community
Intermediate
mmmmmm786mngb-jpgmmmmmm786mngb-jpg

meta-remove

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

Community
Advanced
Dach-CoinDach-Coin
33

meta-remove

Remove specified metadata objects from exported 1C configuration dumps.

Community
Intermediate
Arman-KudaibergenovArman-Kudaibergenov
151

meta-remove

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

Community
Intermediate