form-remove

Removes named forms from objects in 1C source trees and updates XML metadata.

33|8|Updated Mar 6, 2026
One-click install
npx skills add https://github.com/Dach-Coin/claude_rules_1c --skill form-remove-dach-coin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: form-remove
Source: https://github.com/Dach-Coin/claude_rules_1c/tree/main/.claude/skills/form-remove
Command: npx skills add https://github.com/Dach-Coin/claude_rules_1c --skill form-remove-dach-coin

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill solves the problem of deleting an unwanted 1С form (in reports, processing, catalogs, documents, etc.) while keeping the root metadata XML consistent and preventing broken registrations.

Core Features & Use Cases

  • Removes form metadata files and folders for the specified form name under the target 1С object.
  • Updates the root object XML by removing the corresponding <Form> entry from ChildObjects.
  • Clears DefaultForm when it points to the deleted form to avoid runtime/UI references to a non-existent form.
  • Use case: You need to retract a UI form from an object after refactoring (e.g., deprecating an old report layout) and ensure the platform no longer references it.

Quick Start

Tell the AI: Remove the form "<FormName>" from the 1С object "<ObjectName>" in the src directory.

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 an object and update the root metadata XML?

Removing a 1C form involves deleting its metadata files and folder, then updating the root object XML to drop the corresponding ChildObjects entry. This prevents broken registrations and keeps metadata consistent.

What happens to DefaultForm when I delete a 1C form?

When deleting a 1C form, the DefaultForm reference is automatically cleared if it points to the removed form. This prevents runtime and UI references to a non-existent form.

Why do I need to edit the root object XML when deleting 1C form metadata?

Editing the root object XML is required to drop the ChildObjects entry for the deleted form. Simply deleting form metadata files without updating the XML leaves broken registrations and inconsistent 1C metadata.

Does 1C form removal preserve the UTF-8 BOM in the root object XML?

Yes, 1C form removal writes back the updated root object XML while preserving the UTF-8 BOM. XML edits are performed in the md namespace to ensure deterministic and safe metadata execution.

Can I use this 1C form removal for deprecating obsolete UI variants after refactoring?

Yes, this 1C form removal handles source-tree maintenance tasks like deprecating forms after refactoring and cleaning up obsolete UI variants. It validates the root XML and form metadata before executing deletion.

What is the best way to clean up obsolete 1C form metadata files from a source tree?

The best way to clean up obsolete 1C form metadata is a deterministic process that deletes form files and folders, updates the root XML ChildObjects entry, and clears DefaultForm references to maintain platform consistency.