subsystem-edit

Edit 1C subsystem XML Content, ChildObjects, and Properties.

41|5|Updated May 28, 2026

Search Tags:#automation #configuration #xml #edit #subsystem #1c

Ready to run

npx skills add https://github.com/msrv-tech/skills --skill subsystem-edit-msrv-tech

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: subsystem-edit
Source: https://github.com/msrv-tech/skills/tree/main/subsystem-edit
Command: npx skills add https://github.com/msrv-tech/skills --skill subsystem-edit-msrv-tech

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill enables precise edits of 1C subsystem XML configurations, allowing you to modify Content, manage ChildObjects, and adjust Properties without manual XML hand-editing.

Core Features & Use Cases

Edit specific subsystem XML elements to add or remove content entries, manage child subsystems, and set properties.
Automate common configuration tasks in development, testing, and deployment environments.
Use Case: Update a subsystem to include a new Document.Заказ in Content or to enable/disable a feature via IncludeInCommandInterface.

Quick Start

Edit Subsystems/Sales.xml to add Document.SalesOrder to Content and set IncludeInCommandInterface to false.

Frequently Asked Questions about subsystem-edit

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

FAQPage Schema

How do I automate 1C subsystem XML edits for configuration changes?▼

Automating 1C subsystem XML edits involves modifying Content, ChildObjects, and Properties elements using targeted scripting operations. This approach replaces manual XML hand-editing by supporting add-content, remove-content, add-child, remove-child, and set-property actions with optional validation.

Can I add a new document to 1C subsystem Content without manual XML editing?▼

Adding a document to 1C subsystem Content without manual XML editing is possible using the add-content operation. This targeted edit automatically inserts the required content entries into the subsystem configuration file, ensuring precise and repeatable modifications.

How do I manage child subsystems in 1C configuration XML files?▼

Managing child subsystems in 1C configuration XML files requires using add-child and remove-child operations. These actions modify ChildObjects elements and can automatically create necessary stubs for new children, ensuring structural integrity during development or deployment workflows.

Is it possible to set 1C subsystem properties like IncludeInCommandInterface programmatically?▼

Setting 1C subsystem properties such as IncludeInCommandInterface programmatically is supported through the set-property operation. This enables precise adjustments to subsystem configuration elements, allowing you to enable or disable features without directly modifying the underlying XML.

What are the limitations of automating 1C subsystem configuration edits?▼

Automating 1C subsystem configuration edits focuses specifically on modifying Content, ChildObjects, and Properties elements. It does not handle broader configuration structure changes outside the subsystem scope, and users should apply optional validation to prevent invalid XML structures during automated deployment workflows.

Does the 1C subsystem edit script support deployment workflows?▼

1C subsystem edit scripts support deployment workflows by applying precise, repeatable XML modifications to configuration files. They integrate into development, testing, and deployment environments to automate common subsystem configuration tasks like content updates and property adjustments.