skills.rest
Nikolay-Shirokov
Nikolay-ShirokovCOMMUNITY
Explore all skills by this author →
GitHub

db-repo

Manages 1C:Enterprise configuration repository operations including locking, committing, and updating objects.

578|108|Updated Feb 8, 2026
Search Tags:#Version Control#powerShell#infobase#1C:Enterprise#1cv8 designer#lock commit update#configuration repository
One-click install
npx skills add https://github.com/Nikolay-Shirokov/cc-1c-skills --skill db-repo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: db-repo
Source: https://github.com/Nikolay-Shirokov/cc-1c-skills/tree/main/.claude/skills/db-repo
Command: npx skills add https://github.com/Nikolay-Shirokov/cc-1c-skills --skill db-repo

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Team development on 1C:Enterprise 8.3 configurations requires coordinating changes through the configuration repository (хранилище конфигурации): capturing objects before editing, committing changes with comments, and pulling colleagues' updates without silently rolling back their work. Doing this through the Designer CLI by hand is error-prone — exit codes do not reflect actual results, partial locks go unnoticed, and stale sources can silently overwrite others' changes.

Core Features & Use Cases

  • Object lock/unlock/commit/update cycle: Capture configuration objects (including forms, templates, and commands via -WithChildren), commit changes with multi-line comments, and fetch updates from the repository, with per-object parsing of the platform log.
  • Repository administration: Connect/disconnect infobases, create repositories, manage users and rights, view version history reports, dump versions to CF files, set labels, and clear caches (detailed in references/).
  • Safety guardrails: Automatic re-dump warnings when lock/update pulls fresh versions, resolution of non-lockable child objects (attributes, tabular sections) to their owners, and confirmation prompts before destructive operations like unlock -Force or disconnect.
  • Use Case: Before editing the Номенклатура catalog, run lock to capture it, edit the XML sources, load them back partially, then commit with a comment — the skill warns you if the lock pulled newer versions that must be re-dumped first.

Quick Start

Ask the AI to capture the catalog Справочник.Номенклатура in the configuration repository of your infobase, then commit the changes with a comment after your edits are loaded.

Frequently Asked Questions about db-repo

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

FAQPage Schema
How do I lock and commit objects in a 1C configuration repository from the command line?▼

Run the db-repo script with -Command lock and -Objects listing names like Справочник.Номенклатура, edit the sources, load them back, then run -Command commit with -Comment. The script wraps the 1cv8 Designer /ConfigurationRepositoryLock and /ConfigurationRepositoryCommit batch keys.

How to update a 1C infobase from the configuration repository?▼

Use the update subcommand, which invokes /ConfigurationRepositoryUpdateCfg to pull changes from the repository into the local configuration. If objects were received, the script prints a ready-made partial re-dump command so stale sources do not silently roll back colleagues' changes.

Can I lock individual attributes or tabular sections in a 1C repository?▼

No. Attributes, tabular sections, dimensions, and resources are not separate repository objects; only the owner object, its forms, templates, and commands can be locked. The script automatically resolves such names to the owner object and prints a note.

Why does the 1C repository command return exit code 0 but change nothing?▼

The platform reports no-op outcomes like already-locked or nothing-to-commit with exit code 0, and partial locks can return code 1. The script parses the operation log line by line and reports per-object results instead of relying on the exit code.

Does the 1C configuration repository work with extensions?▼

Yes. Extensions have their own repository with a separate path. Pass -Extension with the extension name, and the script reads credentials from the extensions[].repository entry in .v8-project.json; all subcommands work identically for extensions.

Which 1C repository operations require user confirmation before running?▼

Locking the entire configuration with -All, unlock -Force which discards local edits, disconnect which removes the binding on the repository side, and connect -ForceReplaceCfg which replaces the infobase configuration all require explicit user confirmation.

Related Skills

Explore More Software Engineering Skills→
msrv-techmsrv-tech
41

db-load-git

Automate loading Git-tracked 1C configuration changes into an infobase.

Community
Advanced
Dach-CoinDach-Coin
33

db-dump-xml

Dump 1C configuration metadata into XML files via DumpConfigToFiles.

Community
Intermediate
kivo360kivo360
1

moai-change-logger

Track and audit project changes across files, code, and repository history.

Community
Advanced
msrv-techmsrv-tech
41

db-dump-xml

Export 1C configuration to XML files using v8 path and credentials.

Community
Intermediate