skills.rest
msrv-tech
msrv-techCOMMUNITY
Explore all skills by this author →
GitHub

interface-edit

Edit 1C CommandInterface.xml to control command visibility and placement.

41|5|Updated May 28, 2026
Search Tags:#ordering#placement#xml-edit#1c#commandinterface#interface-edit#show-hide
One-click install
npx skills add https://github.com/msrv-tech/skills --skill interface-edit-msrv-tech
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: interface-edit
Source: https://github.com/msrv-tech/skills/tree/main/interface-edit
Command: npx skills add https://github.com/msrv-tech/skills --skill interface-edit-msrv-tech

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires lxml, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This skill streamlines the management of the 1C CommandInterface.xml by allowing precise visibility, grouping, and ordering of commands across subsystems without manual XML edits.

Core Features & Use Cases

  • Hide or show commands in the CommandInterface.xml to tailor tools for specific roles or workflows.
  • Place commands into groups and adjust their order, and set subsystems and groups ordering.
  • Use Case: customize 1C UI for a project with Sales and Purchasing subsystems to limit user actions and improve navigation.

Quick Start

Run the interface-edit script with a target CommandInterface.xml path and an operation to apply the desired changes.

Frequently Asked Questions about interface-edit

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

FAQPage Schema
How do I hide or show commands in 1C CommandInterface.xml?▼

To hide or show commands in 1C CommandInterface.xml, run the interface-edit script with a target file path and a visibility operation. It performs in-place XML modifications to tailor tools for specific roles or workflows without manual edits.

What is the best way to automate command ordering in 1C configurations?▼

Automating command ordering in 1C configurations is best handled by running the interface-edit script on a valid CommandInterface.xml path. It adjusts placement and ordering across subsystems and command groups automatically.

Does the 1C interface-edit script require any specific dependencies?▼

The 1C interface-edit script requires the lxml dependency. You need a valid CommandInterface.xml path and the PowerShell or Python scripts to perform the in-place XML modifications with optional validation.

Can I customize 1C UI command groups for different subsystems automatically?▼

You can customize 1C UI command groups for different subsystems automatically by applying the interface-edit script. It places commands into groups and sets subsystem and group ordering directly in the CommandInterface.xml file.

Why does my 1C CommandInterface visibility change require an XML edit?▼

1C CommandInterface visibility changes require XML edits because the configuration stores command placement and visibility settings in CommandInterface.xml. The interface-edit script automates these precise in-place modifications to prevent manual XML errors.

Related Skills

Explore More Software Engineering Skills→
IngvarConsultingIngvarConsulting
140

interface-validate

Validate CommandInterface.xml structure in 1C projects for configuration errors.

Official
Basic
Alex1980AlexAlex1980Alex

interface-edit

Edit 1C CommandInterface.xml files with validation-aware, namespace-preserving changes.

Community
Advanced
mmmmmm786mngb-jpgmmmmmm786mngb-jpg

interface-edit

Toggle command visibility and organize groups in 1C CommandInterface.xml via YAML/JSON inputs.

Community
Intermediate
Alex1980AlexAlex1980Alex

interface-validate

Validate 1C CommandInterface.xml structure and command references for subsystems.

Community
Intermediate