skills.rest
Arman-Kudaibergenov
Arman-KudaibergenovCOMMUNITY
Explore all skills by this author →
GitHub

db-list

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

151|20|Updated Feb 11, 2026
Search Tags:#automation#project setup#json#1c#database registry#git branch mapping#connection parameters
One-click install
npx skills add https://github.com/Arman-Kudaibergenov/1c-ai-development-kit --skill db-list-arman-kudaibergenov
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: db-list
Source: https://github.com/Arman-Kudaibergenov/1c-ai-development-kit/tree/main/.claude/skills/db-list
Command: npx skills add https://github.com/Arman-Kudaibergenov/1c-ai-development-kit --skill db-list-arman-kudaibergenov

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the hassle of manually tracking which 1C information bases your project can use by keeping a single, readable registry in .v8-project.json.

Core Features & Use Cases

  • Database inventory and visibility: shows all registered bases with their IDs, aliases, and connection-relevant fields.
  • Interactive registry updates: lets you add or remove bases in a structured, consistent way without editing JSON by hand.
  • Correct target resolution by intent: selects the appropriate database for other db-* skills by id/alias/name, or by mapping the current Git branch to databases[].branches, falling back to default or asking the user when ambiguous.

Quick Start

Ask an AI assistant to list all available bases from the project's .v8-project.json for your current workflow.

Frequently Asked Questions about db-list

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

FAQPage Schema
How do I manage multiple 1C database connections in a single project?▼

A 1C database registry resolves target databases by mapping current Git branches to specific bases using .v8-project.json, falling back to a default database or prompting for user clarification when the branch mapping is ambiguous.

What is the best way to map Git branches to specific 1C information bases?▼

Mapping Git branches to 1C information bases is handled through a .v8-project.json registry, which automatically resolves the correct database target by matching the current branch name to configured branch mappings.

How do I add a new 1C information base to my project setup without editing JSON manually?▼

You can add a new 1C information base through interactive data entry that updates the .v8-project.json registry automatically, ensuring structured and consistent connection parameters without manually editing the JSON file.

Can I view all registered 1C databases and their connection parameters in one place?▼

Viewing all registered 1C databases is supported by the .v8-project.json registry, which provides a complete inventory of all configured bases along with their IDs, aliases, and connection-relevant fields.

Does resolving a target 1C database require a default fallback when the Git branch is unmapped?▼

Resolving a target 1C database uses a default fallback when the current Git branch has no explicit mapping in the .v8-project.json registry, and it will ask for user clarification if the target remains ambiguous.

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
comolcomol
413

1c-platform-ops

Automate batch operations for 1C:Enterprise build, dump, and configuration exchange.

Community
Intermediate
Dach-CoinDach-Coin
33

db-update

Apply 1C configuration changes to a target database via UpdateDBCfg.

Community
Intermediate
Alex1980AlexAlex1980Alex

db-dump-xml

Export 1C configuration databases to XML files.

Community
Advanced