1c-platform-ops

Automate batch operations for 1C:Enterprise build, dump, and configuration exchange.

413|90|Updated Aug 31, 2025
One-click install
npx skills add https://github.com/comol/cursor_rules_1c --skill 1c-platform-ops
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: 1c-platform-ops
Source: https://github.com/comol/cursor_rules_1c/tree/main/.cursor/skills/1c-platform-ops
Command: npx skills add https://github.com/comol/cursor_rules_1c --skill 1c-platform-ops

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

Batch operations on the 1C:Enterprise platform, including building/dumping data processors, loading/dumping configurations and extensions, and launching Enterprise or Designer.

Core Features & Use Cases

  • Build or dump external data processors (EPF/ERF) from XML and deploy to EPF/ERF files.
  • Load and dump configurations and extensions to and from XML directories.
  • Launch 1C:Enterprise or Designer for testing and development workflows.

Quick Start

Run the provided scripts from the project root to build, dump and load configurations and launch 1C tools.

Frequently Asked Questions about 1c-platform-ops

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

FAQPage Schema
How do I automate batch operations for 1C:Enterprise platform configurations from the command line?

Batch 1C:Enterprise operations are automated using command-line scripts to build and dump external data processors, load configurations from XML, and manage extensions without manual Designer interaction.

How do I build or dump external data processors like EPF and ERF files from XML?

Building or dumping EPF and ERF files from XML is handled by dedicated batch scripts that compile external data processors and deploy them directly to EPF or ERF file formats.

Can I load and dump 1C extensions and configurations to XML directories using batch scripts?

Loading and dumping 1C extensions and configurations to XML directories is supported by batch scripts that extract and apply configuration exchange data for environment management.

Do I need to launch 1C:Enterprise or Designer manually when running batch configuration scripts?

Launching 1C:Enterprise or Designer is automated by the batch scripts, allowing testing and development workflows to execute directly from the command line without manual application startup.

What is the best way to manage 1C extension configuration exchange across multiple environments?

Managing 1C extension configuration exchange across environments is best handled by batch scripts that dump configurations to XML and load extensions programmatically for consistent deployment.

Why does my 1C configuration load from XML fail when running batch operations from the project root?

1C configuration load failures during batch operations often occur when scripts are not executed from the project root or when XML directory structures do not match the expected configuration exchange format.