db-load-git

Load Git configuration changes into a 1C database via partial reload.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires git, powershell, 1cv8.exe, and includes scripts (resource) components.

What problem does it solve?

Этот навык решает проблему ручной и полной загрузки конфигурации в 1С при каждом изменении, позволяя загружать в информационную базу только те элементы, которые были затронуты в Git.

Core Features & Use Cases

  • Частичная загрузка по Git-изменениям: определяет измененные файлы конфигурации через git diff (staged/unstaged/commit/all).
  • Гибкий выбор источника изменений: поддерживаются режимы All (по умолчанию), Staged, Unstaged, Commit с диапазоном коммитов.
  • Поддержка объектов и Ext: для не-XML файлов корректно мапит изменения на объектные XML и добавляет связанные файлы из каталогов Ext/.
  • Опциональный DryRun и UpdateDB: можно сначала посмотреть, что будет загружено, и при необходимости сразу применить обновление БД конфигурации.

Quick Start

Запусти загрузку всех незафиксированных изменений из Git в указанную файловую базу 1С, выполнив: /db-load-git dev -Source All -ConfigDir <path-to-git-xml-export>.

Frequently Asked Questions about db-load-git

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

FAQPage Schema
How do I load only Git changes into a 1C database instead of doing a full configuration reload?

You can load only Git changes into a 1C database by detecting configuration file diffs and executing 1cv8 DESIGNER with partial loading, targeting modified XML files and Ext/ artifacts to skip unchanged elements.

What's the best way to apply staged or unstaged Git changes to a 1C infobase?

To apply staged or unstaged changes to a 1C infobase, use source selection modes like Staged, Unstaged, or All. The tool derives the config file list from these Git diffs and executes a partial load via 1cv8 DESIGNER.

Can I load 1C configuration changes from a specific commit range?

Yes, you can load 1C configuration changes from a specific commit range using the Commit mode. This identifies all configuration file modifications within the specified commit range and applies them through partial loading in 1cv8 DESIGNER.

How do non-XML configuration files map to 1C objects during a partial Git load?

During a partial Git load, non-XML files map to their corresponding object-level XML files, and related artifacts from Ext/ directories are added to the load scope to ensure 1C configuration integrity.

Do I need a .v8-project.json file to identify the target 1C infobase for configuration loading?

You need either a .v8-project.json file or explicit connection parameters to identify the target 1C infobase. This identification is required to execute the 1cv8 DESIGNER partial loading process correctly.

Can I preview which 1C configuration files will be loaded before applying changes?

Yes, you can preview which 1C configuration files will be loaded by using the optional DryRun mode. This shows the exact file list derived from Git diffs before executing the actual 1cv8 DESIGNER partial load.