form-remove

Removes a form from a 1C:Enterprise object and cleans its XML registration.

1|2|Updated Jul 19, 2026
One-click install
npx skills add https://github.com/IngvarConsulting/unica-marketplace --skill form-remove-ingvarconsulting
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: form-remove
Source: https://github.com/IngvarConsulting/unica-marketplace/tree/main/plugins/unica/skills/form-remove
Command: npx skills add https://github.com/IngvarConsulting/unica-marketplace --skill form-remove-ingvarconsulting

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Removing a form from a 1C:Enterprise configuration object (catalog, document, report, data processor) requires deleting the form's XML metadata and directory, plus manually cleaning up references in the object's root XML file. Doing this by hand is error-prone and can leave dangling registrations or broken default form slots. ## Core Features & Use Cases - Complete form removal: Deletes the form's XML metadata file and its entire directory recursively from the source tree. - Automatic registration cleanup: Removes the <Form> entry from ChildObjects in the object's root XML and clears any Default*Form or Auxiliary*Form slot that referenced the deleted form. - Safe mutation workflow: Runs through the unica MCP tool with a dry-run default, so changes are only applied when explicitly confirmed, and vendor support locks are respected. - Use Case: You are refactoring a 1C catalog and need to drop an obsolete form "СтараяФорма" from the "Номенклатура" object without manually editing XML files. ## Quick Start Ask the assistant to remove the form named СтараяФорма from the Номенклатура object in the src directory using the unica form removal tool.

Frequently Asked Questions about form-remove

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

FAQPage Schema
How do I delete a form from a 1C object?▼

Call the unica.form.remove MCP tool with the ObjectName, FormName, and SrcDir parameters. It deletes the form's XML file and directory, then removes the form registration from the object's root XML automatically.

What happens to default form references when a 1C form is deleted?▼

If the deleted form was assigned to a Default*Form or Auxiliary*Form slot, that slot's value is cleared automatically. Emptied XML elements are preserved in self-closing form such as <ChildObjects/>.

Does form removal support a dry run before applying changes?▼

Yes, the unica.form.remove tool defaults to a dry run. The dryRun parameter is only set to false when the user explicitly requests the mutation, preventing accidental source modifications.

Can I remove a form from a vendor-locked 1C object?▼

The vendor support guard inside unica blocks edits to locked or read-only supported objects. In that case, use a CFE extension or an explicit support-state change plan instead of editing raw support metadata.

Which 1C object types support form removal?▼

The skill works with any 1C:Enterprise object that owns forms, including data processors, reports, catalogs, and documents. The form is removed from the object's Forms directory under the specified source folder.