form-remove

Remove a 1C form and update root XML metadata references.

Updated Mar 29, 2026
One-click install
npx skills add https://github.com/Alex1980Alex/1C-Framework --skill form-remove-alex1980alex
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: form-remove
Source: https://github.com/Alex1980Alex/1C-Framework/tree/main/external/cc-1c-skills/.claude/skills/form-remove
Command: npx skills add https://github.com/Alex1980Alex/1C-Framework --skill form-remove-alex1980alex

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill removes an obsolete form from a 1C object while keeping the source metadata consistent, so you do not have to manually edit multiple XML files and folders.

Core Features & Use Cases

  • Form deletion: Deletes the form metadata file and the form directory when they exist.
  • Metadata cleanup: Removes the form registration from the object's root XML and clears the default form reference if it points to the removed form.
  • Deterministic maintenance: Uses a scripted workflow for repeatable updates to 1C processing, report, catalog, document, and other object types.
  • Use case: Cleanly remove a deprecated form from a configuration package without leaving stale references behind.

Quick Start

Tell the assistant to remove the specified form from the target 1C object and update the corresponding source metadata safely.

Frequently Asked Questions about form-remove

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

FAQPage Schema
How do I remove a 1C form from a configuration package without leaving stale metadata references?

To remove a 1C form cleanly, you must delete the form XML and its directory, then update the object's root XML to clear ChildObjects entries and any DefaultForm reference pointing to the removed form.

What happens to the default form reference when deleting a 1C form from source metadata?

When deleting a 1C form, the default form reference in the object's root XML must be cleared if it points to the removed form, ensuring the processing, report, catalog, or document metadata remains consistent.

Can I use Python and lxml to automate 1C metadata cleanup for deprecated forms?

Yes, you can automate 1C metadata cleanup using Python scripts with lxml to parse and modify the XML files, ensuring deterministic deletion of form directories and consistent root XML updates.

What is the best way to safely delete 1C processing and report object forms from the source tree?

The best way to delete 1C forms safely is using a scripted workflow that deterministically removes the form directory and updates the root XML, preventing broken references in processing and report objects.

Does removing a 1C form manually break the configuration metadata?

Manual 1C form removal often breaks configuration metadata because it leaves stale references in the root XML; a scripted approach ensures all ChildObjects and DefaultForm entries are updated correctly.