subsystem-info

Parses 1C subsystem XML exports to reconstruct hierarchy and command interfaces.

33|8|Updated Mar 6, 2026

Search Tags:#reverse engineering #hierarchy #1c #xml parsing #structure analysis #command interface #subsystem xml

Ready to run

npx skills add https://github.com/Dach-Coin/claude_rules_1c --skill subsystem-info-dach-coin

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: subsystem-info
Source: https://github.com/Dach-Coin/claude_rules_1c/tree/main/.claude/skills/subsystem-info
Command: npx skills add https://github.com/Dach-Coin/claude_rules_1c --skill subsystem-info-dach-coin

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill turns raw 1C subsystem XML exports into a readable, navigable overview of subsystem composition, hierarchy, and CommandInterface.xml integration.

Core Features & Use Cases

Subsystem structure analysis: Summarizes subsystem properties and lists included contents grouped by object type.
Hierarchy exploration (tree): Builds a recursive tree of child subsystems with markers indicating CommandInterface presence, use-one-command, and hidden status.
Command interface inspection: Parses CommandInterface.xml to report command visibility, placement, order, and subsystem/group ordering.

Quick Start

Use the subsystem-info skill to generate a tree view from the local Subsystems/ directory at Subsystems/ (folder) by running: subsystem-info <SubsystemPath> -Mode tree.

Frequently Asked Questions about subsystem-info

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

FAQPage Schema

How do I parse 1C subsystem XML exports to understand hierarchy and command interface structure?▼

Parsing 1C subsystem XML exports reconstructs subsystem composition, hierarchy, and CommandInterface.xml structure. It extracts md:Subsystem metadata to list child subsystems, content items, and command visibility grouped by object type for easier navigation.

What is the best way to audit command visibility and placement in CommandInterface.xml?▼

Auditing CommandInterface.xml involves parsing command visibility, placement, order, and subsystem group ordering. The command interface inspection mode extracts these sections to report how commands are positioned and whether they are visible.

Can I generate a tree view of child subsystems from a local 1C Subsystems directory?▼

Generating a tree view of child subsystems from a local Subsystems directory uses the tree mode. It builds a recursive hierarchy with markers indicating CommandInterface presence, use-one-command status, and hidden flags.

How do I drill down into specific 1C subsystem content object types?▼

Drilling down into specific 1C subsystem content object types uses the content mode with optional Name filtering. It summarizes subsystem properties and lists included contents grouped by object type for targeted analysis.

What modes are available for reverse engineering 1C subsystem layout?▼

Reverse engineering 1C subsystem layout supports overview, content, ci, tree, and full modes. Overview summarizes properties, content groups items by type, ci inspects commands, tree builds hierarchy, and full combines all analyses.