db-load-xml

Load 1C configuration metadata from XML files into a target information base.

151|20|Updated Feb 11, 2026
One-click install
npx skills add https://github.com/Arman-Kudaibergenov/1c-ai-development-kit --skill db-load-xml-arman-kudaibergenov
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: db-load-xml
Source: https://github.com/Arman-Kudaibergenov/1c-ai-development-kit/tree/main/.claude/skills/db-load-xml
Command: npx skills add https://github.com/Arman-Kudaibergenov/1c-ai-development-kit --skill db-load-xml-arman-kudaibergenov

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill solves the problem of repeatedly importing 1C:Enterprise 8.3 configuration metadata from XML sources into an existing information base, reducing manual copy-and-compile steps and preventing inconsistent deployments.

Core Features & Use Cases

  • Full and Partial XML Loading: Performs complete configuration replacement (Full) or targeted updates of selected files (Partial).
  • Flexible Connection Resolution: Automatically determines platform and resolves the target database using .v8-project.json and/or git branch mappings, while allowing explicit connection parameters.
  • Operational Safety Guardrails: Warns that full loading replaces the entire configuration and should be confirmed by the user before execution.

Use case example: you maintain XML configuration dumps in a workspace and need to apply them to a dev database, either as a full refresh or by updating only a few changed objects (e.g., forms or modules).

Quick Start

Ask to load the XML configuration from a directory into the specified database by running /db-load-xml <configDir> <database> in the chat.

Frequently Asked Questions about db-load-xml

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

FAQPage Schema
How do I load 1C configuration from XML files into a database?

This process applies XML metadata to an information base via the LoadConfigFromFiles workflow. You can execute it by providing the configuration directory and target database details to apply your saved XML sources.

Can I perform a partial update of 1C metadata using only specific XML files?

Yes, you can perform a partial update of 1C metadata by selecting specific XML files for targeted object loading. This Partial mode applies incremental updates to changed objects like forms or modules without replacing the entire configuration.

How does the database connection get resolved when importing 1C XML configurations?

The database connection for importing 1C XML configurations is resolved automatically using .v8-project.json and git branch mappings. You can also provide explicit connection parameters to route the metadata load to the correct target information base.

What is the difference between full and partial XML configuration loading in 1C?

Full XML configuration loading completely replaces the entire existing 1C configuration in the information base, while Partial loading applies incremental updates exclusively to selected files. Full mode requires user confirmation before execution due to operational safety guardrails.

Are there safety precautions when doing a full 1C configuration replacement from XML?

Yes, operational safety guardrails warn that full loading replaces the entire configuration and requires user confirmation before execution. This prevents inconsistent deployments by ensuring you intentionally overwrite the existing information base metadata.