template-remove

Remove a template from a 1C object and update its root XML.

Updated Feb 21, 2026

Search Tags:#automation #maintenance #scripts #xml #object #1c #template-removal

Ready to run

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

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Removing templates from 1C objects and unregistering them from the root XML, simplifying configuration cleanup and preventing stale references.

Core Features & Use Cases

Remove a specified template from a 1C object's Templates folder, including its metadata and template directory.
Update the root object's XML to drop the Template from ChildObjects and clear references in MainDataCompositionSchema when applicable.
Useful during maintenance, configuration updates, or migration when templates are deprecated or replaced.

Quick Start

Invoke the template-remove command with the target object and template names to delete a specific template from a 1C object.

Frequently Asked Questions about template-remove

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

FAQPage Schema

How do I remove a template from a 1C object and update the root XML?▼

Removing a template from a 1C object deletes its metadata, clears the template directory, and updates the root XML to drop ChildObjects references and clear MainDataCompositionSchema attributes. This prevents stale template references during configuration maintenance.

What is the best way to unregister deprecated templates from 1C configurations?▼

Unregistering deprecated templates involves deleting the template directory from the object's Templates folder and modifying the root object XML. This ensures configuration cleanup and prevents broken references when templates are replaced or deprecated during updates.

Does the template removal script work with all 1C object types like catalogs and documents?▼

Yes, the template removal script processes various 1C objects including processing, reports, catalogs, and documents. It targets the specified template within the object's Templates folder and ensures root XML updates to maintain configuration integrity.

Why does my 1C configuration still reference a deleted template in the root XML?▼

Stale template references occur when the root object XML is not updated after deletion. Proper template removal requires dropping the template entry from ChildObjects and clearing MainDataCompositionSchema references to ensure the configuration remains valid and clean.

Do I need lxml installed to run 1C template removal scripts?▼

Yes, the lxml dependency is required to parse and modify the root object XML files. The script uses lxml to accurately locate and remove template metadata, ChildObjects entries, and MainDataCompositionSchema references during the cleanup process.

When should I clean up templates from 1C objects during configuration maintenance?▼

Clean up templates during maintenance, configuration updates, or migrations when templates become deprecated or replaced. Removing unused templates and unregistering them from the root XML prevents stale references and keeps the configuration streamlined and error-free.