db-dump-xml

Dump 1C configurations to XML source files via DumpConfigToFiles.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Manually exporting a 1C configuration to XML is slow and error-prone, making it difficult to review changes in Git and keep ConfigDumpInfo consistent across runs.

Core Features & Use Cases

  • XML configuration dump to files: Exports configuration sources using 1C’s DumpConfigToFiles into a target folder in either hierarchical or plain format.
  • Full / incremental / partial / info-only modes: Supports full export, incremental changes via ConfigDumpInfo.xml, selective object export, or updating only ConfigDumpInfo.xml.
  • Git-friendly workflow preparation: Prepares exported sources for committing by ensuring the dump output is refreshed according to the chosen mode.

Quick Start

Use db-dump-xml when you need to dump an entire 1C database configuration into XML source files for committing to Git.

Frequently Asked Questions about db-dump-xml

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

FAQPage Schema
How do I export a 1C configuration to XML for Git version control?

To export a 1C configuration to XML, the Skill invokes DumpConfigToFiles to write source files into a target folder. It supports both hierarchical and plain formats, preparing the output for reliable Git commits.

Can I export only specific metadata objects from a 1C configuration?

Yes, partial exports of specific metadata objects are supported. You can selectively dump individual configuration components instead of performing a full export, allowing targeted updates to your XML source files.

Does the 1C XML export tool support incremental changes based on ConfigDumpInfo?

Yes, incremental change exports are supported via ConfigDumpInfo.xml. This mode refreshes the dump output to include only configuration changes, ensuring consistency across runs and simplifying Git reviews of modified metadata objects.

What is needed to run a 1C configuration dump on a server-base setup?

For a server-base setup, you must provide InfoBaseServer and InfoBaseRef. The Skill resolves the 1C runtime path from .v8-project.json or auto-detects it to invoke DumpConfigToFiles correctly.

Why is manually exporting a 1C configuration to XML problematic?

Manual 1C XML exports are slow and error-prone, making it difficult to review Git changes. Automating the configuration dump ensures ConfigDumpInfo stays consistent and correctly applies mode-specific outputs across file-base and server-base setups.