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

db-list

Manage 1C database registry entries in .v8-project.json.

Updated Mar 29, 2026
Search Tags:#aliases#1c#connection strings#project config#database registry#branch matching
One-click install
npx skills add https://github.com/Alex1980Alex/1C-Framework --skill db-list-alex1980alex
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: db-list
Source: https://github.com/Alex1980Alex/1C-Framework/tree/main/external/cc-1c-skills/.claude/skills/db-list
Command: npx skills add https://github.com/Alex1980Alex/1C-Framework --skill db-list-alex1980alex

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you manage the project-wide registry of 1C information bases so you can quickly find, add, inspect, or remove the right database without manually editing configuration files.

Core Features & Use Cases

  • Registry management: Keep .v8-project.json as the source of truth for file and server databases.
  • Database resolution: Match a target base by id, alias, name, current Git branch, or explicit connection parameters.
  • Operational support: View database details, register a new base, or clean up outdated entries when the project changes.
  • Use case: A developer switches branches and needs the correct test base automatically resolved before running a build or dump workflow.

Quick Start

Ask the skill to show the current 1C database list or to add, remove, or inspect a database entry in the project registry.

Frequently Asked Questions about db-list

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

FAQPage Schema
How do I manage 1C database lists in a project configuration?▼

1C database list management involves maintaining a project-wide registry in .v8-project.json to track file and server databases. This approach lets you quickly find, add, inspect, or remove the correct database without manual configuration file editing.

Can I automatically resolve a 1C target database based on my current Git branch?▼

Yes, 1C database resolution supports branch-based selection to automatically match a target base using your current Git branch. It also resolves databases by id, alias, name, or explicit connection parameters before falling back to a default.

How do I add or remove connection strings for 1C file and server databases?▼

Adding or removing 1C database connection strings requires structured updates to .v8-project.json entries. The system handles connection parameter management and prompts for user confirmation when matches are missing or ambiguous.

What is the best way to keep 1C information bases in sync across different project branches?▼

Keeping 1C information bases in sync requires using .v8-project.json as the single source of truth for database aliases and connection parameters. Branch matching automatically resolves the correct test base when developers switch branches for build workflows.

What happens when 1C database alias matching is missing or ambiguous?▼

When 1C database alias matching is missing or ambiguous, the registry resolution process halts and requires explicit user confirmation. This prevents accidental operations on the wrong file or server database before completing any operational task.

Related Skills

Explore More Software Engineering Skills→
Dach-CoinDach-Coin
33

db-list

Manages .v8-project.json registry to resolve 1C target databases by criteria including Git branch.

Community
Intermediate
IngvarConsultingIngvarConsulting
140

v8-runner

Automate 1C runtime workflows including build, dump, load, and testing via MCP commands.

Official
Intermediate
Arman-KudaibergenovArman-Kudaibergenov
151

db-list

Manage .v8-project.json registry entries for 1C databases.

Community
Intermediate
Desko77Desko77
40

1c-db-update

Apply main configuration updates to 1C file-based or server-based databases.

Community
Intermediate