skills.rest
Alex1980Alex
Alex1980AlexCOMMUNITY
Explore all skills by this author →
GitHub

db-load-git

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

Updated Mar 29, 2026
Search Tags:#git#extensions#designer#1c#database sync#partial load
One-click install
npx skills add https://github.com/Alex1980Alex/1C-Framework --skill db-load-git-alex1980alex
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: db-load-git
Source: https://github.com/Alex1980Alex/1C-Framework/tree/main/external/cc-1c-skills/.claude/skills/db-load-git
Command: npx skills add https://github.com/Alex1980Alex/1C-Framework --skill db-load-git-alex1980alex

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill removes the manual work of identifying changed 1C configuration files in Git and loading only those changes into the correct database, which is especially useful when you need a fast partial update instead of a full reload.

Core Features & Use Cases

  • Git-aware change detection: Handles staged, unstaged, commit-range, and all-uncommitted changes.
  • Partial 1C loading: Maps modified module and object files to the correct XML objects and loads only the impacted parts.
  • Operational safeguards: Supports dry-run checks, database resolution from project metadata, extension loading, and optional post-load database updates.
  • Use case: A developer edits several 1C objects in a feature branch, then uses this Skill to preview the affected files and apply the minimal database update needed for testing.

Quick Start

Ask the skill to load the relevant Git changes from your 1C configuration repository into the target database, and mention whether you want a dry run, a commit range, or an extension-specific load.

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 database without a full reload?▼

Loading only Git changes into a 1C database requires mapping modified module files to XML objects via git diff. This applies just the impacted configuration parts to the target database, avoiding a full reload.

Can I preview a 1C configuration update before applying it to the database?▼

Yes, you can preview a 1C configuration update by running a dry-run validation. This checks the selected Git changes before they are applied to the target database, ensuring safe partial imports.

Does this partial 1C loading method support loading configuration extensions?▼

Yes, this partial 1C loading method supports configuration extensions. It detects changed extension files from Git and applies them using the 1cv8 designer, alongside standard staged, unstaged, and committed repository changes.

What is the best way to apply a commit range of 1C changes to a server-based repository?▼

The best way to apply a commit range of 1C changes is by selecting the specific git diff range and mapping those files to XML objects. The tool then loads them into the server-based repository using 1cv8 designer.

How does database resolution work when loading 1C configuration files from Git?▼

Database resolution works by reading project metadata from the .v8-project.json file. This platform resolution mechanism identifies the correct target database automatically before applying the selected Git changes.

Related Skills

Explore More Software Engineering Skills→
mmmmmm786mngb-jpgmmmmmm786mngb-jpg

db-load-git

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

Community
Advanced
Dach-CoinDach-Coin
33

db-load-git

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

Community
Advanced
Dach-CoinDach-Coin
33

db-create

Create 1C:Enterprise 8.3 information bases for file or server deployment.

Community
Intermediate
Arman-KudaibergenovArman-Kudaibergenov
151

db-load-xml

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

Community
Intermediate