db-load-git

Load changed 1C configuration files from Git history into a target infobase.

Updated Feb 21, 2026
One-click install
npx skills add https://github.com/mmmmmm786mngb-jpg/WIM_DEV --skill db-load-git
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: db-load-git
Source: https://github.com/mmmmmm786mngb-jpg/WIM_DEV/tree/main/.cursor/skills/db-load-git
Command: npx skills add https://github.com/mmmmmm786mngb-jpg/WIM_DEV --skill db-load-git

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Automates loading of Git-driven changes into a 1C database by performing partial configuration loads, enabling teams to keep a repository-synced Infobase without full reloads.

Core Features & Use Cases

  • Git-driven change detection and mapping of modified files to 1C configuration objects.
  • Partial loading workflow that updates the infobase without a full reload.
  • Supports All, Staged, Unstaged, and Commit inputs with optional CommitRange and DryRun preview to validate changes before applying.

Quick Start

Run the script from your repository with the required ConfigDir and target infobase arguments to apply Git changes.

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 Git changes into a 1C infobase without a full configuration reload?

To load Git changes into a 1C infobase without a full reload, this Skill identifies modified 1C configuration files from Git history and applies them as a partial update using 1cv8.exe. It reads .v8-project.json to resolve platform paths and executes the partial load directly.

What is partial loading for 1C configuration files and how does it work?

Partial loading for 1C configuration files is the process of mapping modified Git-tracked files to specific 1C objects and updating only those objects in the target infobase. It uses change detection from All, Staged, Unstaged, or Commit sources to avoid full reloads.

Can I preview a 1C configuration load before applying changes to the database?

Yes, you can preview a 1C configuration load before applying changes by using the DryRun option. DryRun allows safe experimentation by validating how Git-detected changes will be processed without actually modifying the target infobase.

What is the best way to apply a specific commit range of 1C configuration changes to a database?

The best way to apply a specific commit range of 1C configuration changes is to use the Commit change source with the optional CommitRange parameter. This targets specific historical updates and loads them as a partial update into the infobase.

Do I need a .v8-project.json file to automate 1C deployment from a Git repository?

Yes, you need a .v8-project.json file to automate 1C deployment from Git because the Skill reads this file to resolve the 1C platform path. Without it, the script cannot locate the 1cv8.exe executable to perform the partial load.