db-load-git

Load changed 1C configuration objects from Git 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-git-arman-kudaibergenov
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: db-load-git
Source: https://github.com/Arman-Kudaibergenov/1c-ai-development-kit/tree/main/.claude/skills/db-load-git
Command: npx skills add https://github.com/Arman-Kudaibergenov/1c-ai-development-kit --skill db-load-git-arman-kudaibergenov

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

It solves the problem of updating a 1C information base by loading only the configuration objects that actually changed in Git, instead of performing slow, full re-imports from XML dumps.

Core Features & Use Cases

  • Partial load by Git diff: Detects changed files from Git (staged, unstaged/untracked, or a commit range) and builds a minimal set of configuration inputs.
  • BSL-to-XML mapping: Converts changed .bsl paths into the correct top-level XML object and includes related Ext/* files for that object.
  • Controlled execution: Supports DryRun to preview what would be loaded, and then performs a partial configuration load into the target 1C DB.
  • Targeted extension loading: Loads into a specified extension or all extensions when requested.
  • Post-run workflow: After loading, it recommends applying changes to the DB via /db-update.

Quick Start

Ask your AI to load staged Git changes into the 1C database named dev using: /db-load-git dev -Source Staged -DryRun.

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-changed 1C configuration files into an information base?

You load partial 1C configuration updates by computing the Git diff and executing a partial XML load. The process filters to changed XML and BSL files, mapping BSL paths to related top-level XML and Ext files.

Can I preview a partial 1C configuration load before applying it?

Yes, you can preview a partial 1C configuration load by enabling the DryRun option. DryRun calculates the minimal set of changed inputs without writing updates to the target information base.

Does partial 1C configuration loading work with staged, unstaged, and commit-range Git diffs?

Yes, partial 1C configuration loading supports staged, unstaged, untracked, and commit-range Git diffs. It resolves the changed file set from your specified source to build minimal configuration inputs.

What is the best way to synchronize a 1C database after loading Git changes?

The best way to synchronize a 1C database after loading Git changes is to apply the modifications to the database. After completing the partial configuration load, you apply the changes to the database via a database update process.

Do I need a .v8-project.json file to load 1C configuration changes from Git?

Yes, you need a .v8-project.json file to load 1C configuration changes from Git. The process requires reading .v8-project.json to resolve the v8path and identify the target base for the partial load.

Why does a partial 1C configuration load map BSL files to XML objects?

A partial 1C configuration load maps BSL files to XML objects because 1C requires top-level XML definitions for module updates. It converts changed .bsl paths into the correct top-level XML object and includes related Ext files.