cf-edit

Edit 1C Configuration.xml properties, ChildObjects, and DefaultRoles via batch operations.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

It solves the problem of safely and precisely updating a 1C Configuration.xml by making targeted edits to configuration properties, the ChildObjects composition, and the DefaultRoles list without having to regenerate everything manually.

Core Features & Use Cases

  • Modify configuration properties: update scalar properties like Version/Vendor/Comment and supported LocalString fields (ru) such as Synonym and DetailedInformation.
  • Adjust configuration composition (ChildObjects): add or remove references in the <ChildObjects> section, keeping canonical ordering by 1C object type.
  • Manage DefaultRoles: add, remove, or replace DefaultRoles entries (supports both Role.X and X role names).
  • Batch operations: apply multiple changes in one run using ";;" separators and/or a JSON DefinitionFile containing an array of operations.

Quick Start

Run cf-edit to set a new configuration version in Configuration.xml at a specific path.

Frequently Asked Questions about cf-edit

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

FAQPage Schema
How do I batch edit 1C Configuration.xml properties without full regeneration?

You can batch edit 1C Configuration.xml by loading operations from a JSON DefinitionFile or using ";;" separators to modify properties, ChildObjects, and DefaultRoles in a single pass without full regeneration.

Can I add and remove DefaultRoles in a 1C configuration file?

You can manage DefaultRoles in a 1C configuration file by applying add-defaultRole, remove-defaultRole, or set-defaultRoles operations, which accept both Role.X and X role name formats.

What's the best way to adjust ChildObjects composition in a 1C Configuration.xml?

Adjust ChildObjects composition in a 1C Configuration.xml by applying add-childObject and remove-childObject operations, which maintain canonical ordering by 1C object type during post-export adjustments.

Does cf-edit support modify-property operations for localized fields like Synonym?

The modify-property operation supports updating scalar properties like Version and Vendor, alongside supported LocalString fields (ru) such as Synonym and DetailedInformation within the 1C Configuration.xml file.

When do I need to patch a 1C Configuration.xml file?

Patching a 1C Configuration.xml is necessary for rollback fixups, post-export adjustments, and metadata or role tuning when applying targeted changes without manually regenerating the entire configuration.

What happens if auto-validation fails during a 1C configuration patch?

When optional auto-validation fails during a 1C configuration patch, the targeted edits to properties, ChildObjects, or DefaultRoles are not applied, ensuring the Configuration.xml remains safe and precise without partial updates.