subsystem-edit

Edit 1C subsystem XML content, child subsystems, and properties.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Eliminates error-prone manual editing of 1C:Enterprise 8.3 subsystem metadata by providing a targeted way to add/remove content, manage child subsystems, and update subsystem properties directly in the subsystem XML.

Core Features & Use Cases

  • Point edits to subsystem XML: update the subsystem’s <Properties> and <ChildObjects> sections without rewriting everything.
  • Content list operations: add or remove objects from the subsystem’s <Content> (supports single item or a JSON array).
  • Child subsystem operations: add or remove entries from <ChildObjects>, and auto-create a stub XML for newly added child subsystems.
  • Property updates: set subsystem properties via set-property, including boolean flags, multilingual fields like Synonym / Explanation, Comment, and Picture.
  • Works with batch definitions: perform multiple operations from a single JSON file (or JSON array) using -DefinitionFile.

Quick Start

Use the subsystem-edit skill to add a Catalog object to the subsystem content by giving it the path to the subsystem XML and the desired operation and value.

Frequently Asked Questions about subsystem-edit

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

FAQPage Schema
How do I edit 1C subsystem XML metadata without rewriting the entire file?

To edit 1C subsystem XML metadata without rewriting everything, you can apply point edits to the `<Properties>` and `<ChildObjects>` sections. This approach updates specific content items and subsystem properties directly, ensuring precise and consistent metadata maintenance.

How do I add or remove objects from a 1C subsystem's content list?

You can add or remove objects from a 1C subsystem's content list by specifying the desired operation and target value. The process supports both single item updates and batch processing via a JSON array for efficient content list management.

Can I update multilingual fields like Synonym and Explanation in 1C subsystem XML?

Yes, you can update subsystem properties including multilingual fields like Synonym and Explanation, as well as Comment, boolean flags, and Picture. This is done using the set-property operation to apply targeted metadata changes.

Does 1C subsystem XML editing support Cyrillic paths and batch operations?

Yes, batch operations are supported using a JSON DefinitionFile, allowing multiple operations from a single file. For Cyrillic paths and values, the system requires parameters to be encoded using UTF-8 Base64.

What happens when I add a new child subsystem to 1C metadata?

When you add a new entry to the `<ChildObjects>` section, the system automatically creates a stub XML file for the newly added child subsystem. This ensures the child subsystem metadata is properly initialized and consistent.

How do I validate 1C subsystem metadata after making XML edits?

After editing 1C subsystem metadata, you can optionally run subsystem-validate for guardrail validation. This ensures the XML edits maintain metadata consistency and adhere to required structural rules.